dholbachgood morning07:48
iulianG'morning dholbach.07:48
dholbachhey iulian07:50
* Laney gnaws on Rhonda08:09
Laneycan you make p.u.c know about saucy pretty please? :-)08:09
Laneywell, it knows about saucy - know about saucy's packages/contents ...08:09
RhondaI think I got the right motivation to investigate further on sunday.08:11
RhondaActually I have no clue what's going on but am fully aware of the issue, have received a fair amount of legit mail about it already08:11
Laneyoh, cool!08:12
Laneyok then sorry for generating further noise :P08:12
LaneyI'll provide you with suitable beverages at debconf to make up for all the traffic ;-)08:12
Laney(I just got a bug report where someone wrongly concluded that a 'broken' (actually not) changelog was breaking p.u.c)08:16
RhondaIt's the changelog's fault !!!1!!!dwarfs!!09:09
Laneyif only it were that simple eh09:10
LaneyRAOF: you left #debian-cli? Anyway, was wondering if you could poke at the gnome-do* FTBFS in unstable? https://bugs.launchpad.net/do/+bug/1097712/10:19
ubottuLaunchpad bug 1097712 in Do "Error building with mono 3" [Undecided,New]10:19
RAOFSure, sometime over the weekend.10:20
Laneythat bug has a patch anyhow10:20
alo21hi... I can't merge cbmc package, due to patch problem15:17
alo21I got: patching file src/ansi-c/c_preprocess.cpp15:20
alo21Hunk #1 FAILED at 590.15:20
alo211 out of 1 hunk FAILED15:20
alo21dpkg-source: info: fuzz is not allowed when applying patches15:20
alo21dpkg-source: info: if patch 'armhf-preprocessing' is correctly applied by quilt, use 'quilt refresh' to update it15:20
alo21dpkg-source: error: LC_ALL=C patc15:21
alo21I run quit-refresh and I got: Nothing in patch minisat-debian15:21
alo21and I can't build the package.. why=15:23
rbasakalo21: try "quilt pop armhf-preprocessing" to go back to that patch, then "quilt refresh" on there, then "quilt push -a" to push them all back again?15:24
alo21rbasak, 'pop armhf-preprocessing' says the patch is not applied15:26
rbasakalo21: oh but hold on - you don't have fuzz, you have a rejection. I think you'll need to examine the patch and fix it up manually.15:26
alo21rbasak, how? what fuzz mean...15:27
alo21the patch seems to be ok15:27
alo21rbasak, I have just weird (i think) line on the third line 'Forwarded: no'15:29
rbasakalo21: fuzz is when the patch context didn't exactly match, but patch was able to guess and apply it anyway. It says "1 out of 1 hunk FAILED" so it looks like the patch doesn't apply at all though.15:29
rbasakalo21: you should be able to run "patch --dry-run -p1 < debian/patches/armhf-preprocessing" without errors.15:29
alo21rbasak, it tells me 'reversed patch detected'15:32
alo21assume -R?15:32
rbasakalo21: perhaps the patch has been adpoted by Debian, so you need to drop it? I check manually in these cases.15:32
alo21rbasak, the patch has been created for Ubuntu only15:33
rbasakalo21: that doesn't mean that Debian or upstream can't take it.15:34
rbasakalo21: you need to check manually why the patch doesn't apply.15:35
paultagForwarded: no patches are almost always troublesome - if anything it should be not-needed or similar15:35
alo21rbasak, debian didn't apply the patch, because that part of file changed15:37
rbasakalo21: OK, so you need to decide if the patch is still needed in Ubuntu. If it is, then you need to fix it up. If it can be dropped, then drop it and note the reason in the changelog.15:38
alo21rbasak, that means that I have to drop that patch.. right?15:38
rbasakWhether or not you can drop the patch depends on the original reason for the patch. Try to avoid a regression.15:38
=== jtechidna is now known as JontheEchidna
alo21rbasak, I solved that problem, but during the building I got: wmm/goto2graph.cpp:935:20: error: 'current_po' may be used uninitialized in this function [-Werror=maybe-uninitialized]  goto_programt* current_po;15:57
rbasakalo21: I'm not really sure how to help you further here. Fixing this kind of issue involves needing a more in-depth knowledge of the specific problem you're getting.15:59
alo21rbasak, c++ programming too?15:59
alo21rbasak, does that error means that the variable is unused?16:00
rbasakalo21: right. Here it looks like the build system forces warnings to be errors. But that suggests that in Debian it does work OK. Perhaps try a Debian chroot to see if it's the Ubuntu toolchain.16:00
rbasakOr perhaps one of the other patches introduces that.16:01
alo21rbasak, it's weird, because the previous devel wrote in changelog: 'cbmc (4.2-6ubuntu1) raring; urgency=low * Don't fail on unused-result warnings.'16:02
rbasakalo21: perhaps he patched it previously?16:20
alo21rbasak, it what?16:20
=== hggdh_ is now known as hggdh
=== dk is now known as Guest47831
=== Amaranthus is now known as Amaranth

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