mkoval | There is a bug in the packaging of Assimp (assimp-3.0~dfsg-2 and -3) shipped with Trusty and Vivid that strips C++ symbols (see this Debian bug report: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=775890>. This makes it impossible to use the C++ API. This has been fixed in assimp-3.0~dfsg-4 by updating 'debian/symbols' file. Can update be applied to Trusty and Vivid? | 16:00 |
---|---|---|
ubot5 | Debian bug 775890 in assimp "assimp: Unresolved symbols in the debian version" [Important,Fixed] | 16:00 |
teward | mkoval: file a bug in Ubuntu against the package, reference that bug and then someone can get to it | 16:13 |
teward | !info assimp trusty | 16:14 |
teward | ooops | 16:14 |
ubot5 | Package assimp does not exist in trusty | 16:14 |
teward | laggy bot | 16:14 |
teward | !info assimp-3.0 trusty | 16:14 |
ubot5 | Package assimp-3.0 does not exist in trusty | 16:14 |
teward | mkoval: you sure it's shipped in Ubuntu? | 16:14 |
teward | there it is | 16:15 |
teward | mkoval: make sure it's fixed in vivid | 16:15 |
teward | mkoval: you may want to wait a couple weeks too, since Utopic is affected and going EOL soon | 16:15 |
mkoval | Package: libassimp3 / Priority: extra / Section: universe/libs | 16:15 |
teward | yes i know i found it via LP | 16:16 |
teward | evil bot doesn't know source packages xD | 16:16 |
teward | oh | 16:16 |
teward | Universe | 16:16 |
mkoval | teward: I built the Vivid source package on Trusty and it fixed the issue | 16:16 |
teward | mkoval: file a bug against the package in Ubuntu anyways | 16:17 |
teward | following the SRU guide - https://wiki.ubuntu.com/StableReleaseUpdates | 16:18 |
teward | mkoval: and it shouldn't fix the issue | 16:18 |
teward | since Vivid is assimp/3.0~dfsg-3 | 16:18 |
teward | not assimp/3.0~dfsg-4 which Debian says fixes it | 16:18 |
mkoval | teward: Sorry, my mistake, I built the Wiley version (not the Vivid) version, which is assimp/3.0~dfsg-4. | 16:20 |
mkoval | s/Wiley/Wily/ | 16:21 |
teward | mkoval: file a bug on the issue, read the SRU link I provided, make test cases etc. and maybe link to a specific patch if one exists | 16:23 |
teward | (we need to know exactly what needs changed to fix it after all) | 16:23 |
teward | the policies might preclude us just taking the wily version and dropping it in :p | 16:23 |
teward | if it's just a symbols change eh | 16:24 |
teward | but the bug still needs filed here in Ubuntu for it | 16:24 |
teward | note though that it'll only be fixed if someone actually goes and preps the debdiff, tests, etc. | 16:24 |
teward | since it's a Universe package | 16:24 |
teward | !universe | 16:24 |
ubot5 | The packages in Ubuntu are divided into several sections. More information at https://help.ubuntu.com/community/Repositories - See https://wiki.ubuntu.com/RecommendedSources for the recommended way to set up your repositories. | 16:24 |
mkoval | teward: I read the SBU guidelines, but wasn't sure if I needed to create a Launchpad issue on it since there is already a Debian issue (and -4 is already released for Wiley). I'm making an issue now. | 16:25 |
mkoval | teward: Thanks for the help. | 16:25 |
teward | mkoval: yes, you do, for tracking purposes | 16:25 |
teward | and, because we aren't Debian xD | 16:26 |
mkoval | teward: I made an issue on Launchpad: <https://bugs.launchpad.net/ubuntu/+source/assimp/+bug/1473503>. From the SBU link, the next step is to post on #ubuntu-bugs. :-) | 16:41 |
ubot5 | Launchpad bug 1473503 in assimp (Ubuntu) "Unresolved symbols in the 3.0~dfsg-2 and 3.0~dfsg-3" [Undecided,New] | 16:41 |
mkoval | s/SBU/SRU. I really can't type today. | 16:49 |
teward | mkoval: OK. note that it's only SRUable if someone produces a patch and such, and since it's in Universe, someone has to produce debdiffs | 16:57 |
teward | (it won't be me since i'm working on nginx right now) | 16:57 |
mkoval | teward: I'd be happy to do it, but I don't know what I need to do. Can you point me to any instructions/documentation about how to produce the necessary patch and diffs? | 16:59 |
teward | i'll take a look at it maybe | 17:00 |
teward | or just leave it for now | 17:00 |
mkoval | teward: ok, thanks | 17:03 |
melodie | hi | 17:24 |
melodie | I wonder if anyone here would have a solution about #1325142 and #1326412 ? | 17:25 |
melodie | bug #1326412 | 17:25 |
ubot5 | bug 1326412 in ubuntu-release-upgrader (Ubuntu) "can't do dist-upgrade due to systemd" [Undecided,Fix released] https://launchpad.net/bugs/1326412 | 17:25 |
melodie | and bug #1325142 seem to be duplicates | 17:26 |
ubot5 | bug 1325142 in systemd (Ubuntu Trusty) "failure to update libpam-systemd in 14.04 due to missing logind init script" [Undecided,Triaged] https://launchpad.net/bugs/1325142 | 17:26 |
melodie | and I can't upgrade the iso under construction anymore :-( | 17:26 |
melodie | I wanted to do the new versions this evening | 17:29 |
melodie | and present them tomorrow in an install party :-( | 17:29 |
melodie | else, how do you boot to upstart? what is the trick there? | 17:29 |
melodie | hi again | 17:51 |
melodie | so what is it that bad bugs aren't fixed in LTS editions? | 17:52 |
teward | melodie: pocket? | 17:53 |
teward | i.e. universe vs. main or such | 17:53 |
melodie | teward beg your pardon? | 17:53 |
melodie | systemd-logind issue | 17:53 |
teward | ah | 17:54 |
melodie | <melodie> bug #1326412 | 17:54 |
ubot5 | bug 1326412 in ubuntu-release-upgrader (Ubuntu) "can't do dist-upgrade due to systemd" [Undecided,Fix released] https://launchpad.net/bugs/1326412 | 17:54 |
melodie | <melodie> and bug #1325142 seem to be duplicates | 17:54 |
ubot5 | bug 1325142 in systemd (Ubuntu Trusty) "failure to update libpam-systemd in 14.04 due to missing logind init script" [Undecided,Triaged] https://launchpad.net/bugs/1325142 | 17:54 |
melodie | this man said it was to be fixed in the release after, but not in Trusty : conclusion, boot to upstart or upgrade. well Trusty _is a LTS, people should not need to upgrade LTS until a new LTS is out. | 17:55 |
melodie | so I am a bit amazed and very confused there | 17:55 |
melodie | and how to boot to upstart anyway when systemd has become a very part of the distro... no idea. I don't think it is possible | 17:56 |
melodie | how can I fix it at least locally? | 17:58 |
melodie | in the meantime? | 17:58 |
melodie | https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1325142/comments/46 | 18:01 |
ubot5 | Launchpad bug 1325142 in systemd (Ubuntu Trusty) "failure to update libpam-systemd in 14.04 due to missing logind init script" [Undecided,Triaged] | 18:01 |
melodie | nobody has a clue? | 18:01 |
melodie | ok I'll lock it up for now | 18:04 |
melodie | locking all systemd packages in that build | 18:07 |
hjd | Hi could someone please mark bug 1404232 as Triaged? :) | 19:26 |
ubot5 | bug 1404232 in cipux-cat-web (Ubuntu) "package cipux-cat-web isn't removable because of failing find command in post-removal script" [Undecided,Confirmed] https://launchpad.net/bugs/1404232 | 19:26 |
hjd | Not quite sure about importance since the problem is uninstallation. High, since it's pretty severe and something you would expect to work? | 19:27 |
hjd | Possibly Critical as I believe uninstallable packages might cause problems when attempting to install other packages... | 19:28 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!