/srv/irclogs.ubuntu.com/2013/03/09/#ubuntu-motu.txt

jdstrandlfaraone: I understand that precise has to be what it is, but oneiric and quantal do not02:45
jdstrand(speaking of the versions)02:46
jdstrandalso, ScottK mentioned the bit about -proposed02:46
jdstrandand I saw the bug, so I wouldn't be able to push that today02:46
jdstrandbut the big issue was the patching02:46
jdstrandmdeslaur: ^02:47
=== altair is now known as Guest59016
Guest59016hello. i could need some help here02:49
Guest59016I did a "bzr branch ubuntu:update-notifier" but it replied me with "Packaging branch status: OUT-OF-DATE" ... so how can I get the current version?02:50
Unit193Why not lp:update-notifier ?02:52
Guest59016what is lp?02:56
Guest59016i have no idea. i just wanted to provide a quick fix there (never done that before) and I found somewhere in the internet, that this is the way to get the code. I dont wqant to apply my fix to an outdated version of the update notifier02:57
Unit193Guest59016: lp is launchpad, it is a "shortcut" name in bazaar.03:07
lfaraonejdstrand: No, really, the + is there for an actually good reason.03:08
lfaraonejdstrand: if you use openafs-modules-source with m-a, upgrades won't work correctly.03:08
jdstrandthat is weird03:09
jdstrandwell, if you didn't already, can you mention it in the bug?03:09
jdstrandthat way the person sponsoring next week won't get tripped up03:10
lfaraonejdstrand: I linked to a comment explaining the rationale, https://bugs.launchpad.net/ubuntu/+source/openafs/+bug/356861/comments/103:10
ubottuLaunchpad bug 356861 in openafs (Ubuntu Jaunty) "OpenAFS Security Advisories 2009-001 and 2009-002" [Undecided,Fix released]03:10
jdstrandoh I see now03:10
jdstrandok, thanks03:10
jdstrandthat seems like a bug in the packaging, but it isn't all that important03:11
lfaraonejdstrand: well, its a module-assistant thing.03:12
lfaraoneAIUI.03:12
Guest59016<Unit193> thanks mate03:14
Unit193Sure.03:14
jdstrandsure, whether it is m-a or openafs, that just seems to not be right, but it doesn't matter. if it needs to be that, it needs to be that03:15
jdstrandwe wouldn't fix that in an SRU03:15
jtaylorI'm guessing that fixing new versions hanging in proposed does not need a ffe?11:17
vibhavjtaylor: They dont add new features, so *probably* not11:36
jtaylorthey do11:36
vibhavjtaylor: ah wait, I read it wrong11:36
* vibhav needs spectacles11:36
vibhavjtaylor: Actually, which fix are you talking about11:37
jtaylorgeneral case11:37
jtaylorwe have many new upstream versions hanging in proposed11:37
vibhavprobably, yes then11:39
vibhavjtaylor: But AFAIK, aren't packages in raring-proposed copied raring after their autopkgtest test is succesfull (if they have one)11:43
jtaylorthey are copied when they build and don't degrade installability11:43
vibhavor is this only before Feature Freeze?11:43
vibhavjtaylor: I think both factors are checked11:44
vibhavjtaylor: The copying probably halts after FF11:46
ScottKNo.  The copying doesn't halt.18:17
ScottKHow else would we upload new stuff.18:17
jtaylorI assumed so much18:17
jtaylorso do we need ffe?18:17
jtayloror leave it broken so it won't migrate18:17
ScottKjtaylor: If you're adding new features, it needs an FFe.  "It's broken and stuck in proposed if we don't ..." makes it an easier decision.18:17
jtaylorsay the ffe is denied, and we need to fix a bug18:18
ScottKWe'll need to decide if it's better to remove it from proposed or take the new feature so it migrates.18:18
jtaylorhow can that be handled?18:18
ScottKWe can remove from proposed, although there will be some potential versioning issues.18:19
ScottKA handful of days after FF, it's somewhat unlikely a well thought out FFe to fix stuff will get denied.18:19
jtaylore.g. libmatio18:20
jtaylorits in proposed and needs a migration18:20
jtaylorblocks bugfixes of other packages (dynare)18:20
ScottKWhat's blocking it?18:20
jtaylorI can't rebuild dynare against libmatio from raring18:21
jtayloronly against proposed18:21
jtaylorso it won't migrate18:21
ScottKRight, but what's blocking libmatio?18:21
jtaylorprobably an ffe18:21
ScottKPaperwork isn't stopping anything18:21
* ScottK looks18:22
jtaylorits certainly all fixable18:22
jtaylorbut kind of a mess18:22
jtaylorI have no idea how invasive the matio change is18:22
ScottKThe first step would be to take the packages that need rebuilding and see if they just build.18:23
ScottKlibscilab2-java, libvips-dev, libvips-tools, libvips15, nip2, python-sciscipy, python-vipscc, scilab, scilab-ann, scilab-celestlab, scilab-cli, scilab-full-bin, scilab-full-bin-dbg, scilab-getfem++, scilab-jims, scilab-minimal-bin, scilab-minimal-bin-dbg, scilab-overload, scilab-plotlib, scilab-scimax, scilab-scimax-doc, scilab-scimysql, scilab-sivp, scilab-swt, scilab-test18:23
ScottKThose are the binaries.18:23
ScottKIt's rather fewer sources.18:23
jtaylorIwas just in the process of checking why its not completed yet18:24
ScottKOK.18:24
jtaylorbut I do need to file a ffe for matio?18:24
ScottKNo.18:24
ScottKNot for the version in proposed'18:24
jtaylorwhile I like that, why? its a new upstream version18:24
ScottKStuff in proposed is already in raring.18:24
jtaylorso no ffe for stuff hanging in proposed ?18:24
ScottKYes.18:24
vibhavScottK: yeah, I had realised that too. Anyway, thanks!18:24
jtaylor19:17 <ScottK> jtaylor: If you're adding new features, it needs an FFe.  "It's broken and stuck in proposed if we don't ..." makes it an easier decision.18:25
ScottKGetting stuff to migrate is bug fixing.18:25
ScottKjtaylor: I thought you needed a newer version with new features than was in proposed already.18:25
jtaylorsorry if I'm dense I'm just trying to learn the new rules18:25
ScottKI misunderstood the question.18:25
jtaylorah ok so just a misunderstanding18:25
ScottKNo problem.  It's the first time around.18:25
ScottKYes.18:25
jtaylorthx, lets see whats wrong with matio18:26
jtaylorscilab does not fill me with confidence :(18:26
ScottKAn example of what I was talking about is if scilab didn't build with the libmatio in raring, but a newer version would.  The new scilab (if it had feature changes) would need an FFe.18:26
ScottKscilab never does.18:27
vibhavScottK: from what I can deduce, you dont need FFEs to have packages in proposed copied to raring, right?18:28
ScottKvibhav: Packages moving to the release pocket from proposed is fully automatic.  No paperwork required.18:29
jtaylorbig surprise scilab fails ._.18:51
* jtaylor wishes people would test build transitions before syncing ._.18:53
ScottKWas that one a manual sync or an automatic one?18:53
ScottKIf it was a manual one, feel free to apply your LART liberally.18:54
jtaylormanual from experimental18:54
ScottKHmmm.18:54
jtaylorhm at least it looks like an easy fix, if scilab would autoreconf...18:56
ScottKGreat.18:57
tumbleweedjtaylor: \o/ for looking at it (I had a look last night, and it scared me)19:02
jtaylorit scares me too :/19:02
jtaylormy build hasn't reached the testsuite yet, thats were it gets ugly19:03
LaneyIf it's too hard, ask the syncer to help you out and failing that we can remove it from proposed (future versioning pain notwithstanding)19:03
tumbleweedwe should grumble at him anyway19:03
tumbleweedI suspect we still people out there with upload rights who aren't aware of britney19:04
tumbleweedand many more who never check to see if their uploads migrated19:04
jtaylorhopefully it was not me why synced it in the end ;)19:04
Laneyeven so, you should be aware of transitions19:05
ScottKUploading a new library and not doing the transition is poor form britney or not.19:05
tumbleweedthere's that too :P19:05
tumbleweeda bunch of stuff stuck in -proposed is due to other installability problems, though19:05
jtaylornoo scilab needs patches to build with the new matio19:06
tumbleweedyeah, I got that far19:06
jtaylordid you start patching?19:07
tumbleweedno, exactly that far :P19:07
tumbleweedand now I need to find something to eat :)19:07
jtaylorlooks like similar to png, move stuff from a public struct to accessors19:07
jtaylorhopefully not more :/19:07
jtaylorwell it compiles19:30
jtaylorhopefully the stuff is tested well :/19:30
* ScottK is fixing the fritzing FTBFS on armhf.19:33
jbichaScottK: thanks :)19:54
ScottKfor?19:54
jbichafritzing in advance19:56
jtaylor5.4.1~git20130308-b7ffdce-1~exp1ubuntu1 what a version number ._.19:58
tumbleweedthat's just silly20:00
jbichajtaylor: does that build on i386? it looked like it had trouble on Debian20:00
jtayloraccording to the changelog the git snapshot should fix that20:01
jtaylorbut I didn't try it yet20:01
ScottKAh.20:15
jtaylorhm -msse in the buildlog of i38620:26
jtaylorhopefully its runtime checked20:26

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