Hi, J.S.Júnior wrote > I’m packaging libburn in version 1.4.0, closes bugs fixed for upstream > And fixe spelling. look my change log.
I seem to be some days ahead of you. Let's coordinate. Please review my changesets and proposed packages. If you see anything that's missing or wrong, then tell me. If you are a DD: be my sponsor. If not: Please do not file a Request For Sponsorship bug before i do. I will inform you about mine (monday evening in europe, when 1 week is over since firect approach attempt). You may then join the bug discussion. Ok for you ? > You check > Needs a sponsor: No for Needs a sponsor: Yes in mentors. That's because i approached some DDs who are related to the topic. But none of them has time, as it seems. > My work in libburn trash now. I'm sorry for that. But if you join the packagers then you need to know this stuff anyway. Plus: You indicate to have found upstream issues. Let's sort them out. > But send for mentors change log version is 1.4.0.1 or 1.4.0-1 or > 1.4.0.1+nmu. I am packaging 1.4.0-1.1 because it is a NMU, thus not 1.4.0-1. (Told so by lintian) > I have more difficult about debhelper 9 and compat version 9. > in build find debian/tmp/usr/lib/libbur….. > but compiling is debian/tp/usr/lib/x86_64-linux-gnu/libburn… http://anonscm.debian.org/viewvc/pkg-libburnia?view=revision&revision=297 > - Bumped Standard-Version to 3.9.6 (no changed needed). I did too. But do not know what it means. :)) > - Added hardening DEB_BUILD_MAINT_OPTIONS This seems to come automatically with debhelper 9. At least the lintian warning ended after the switch. > * Fixed spelling patch: > - fix-spelling-mmc.c > - fix-spelling-libdax_msgs.h > - fix-spelling-cdrskin.1. Please let's discuss this upstream first. Send the change proposals to me directly or to bug-xorr...@gnu.org or to pkg-libburnia-de...@lists.alioth.debian.org. > - Update watch for search signature Did too http://anonscm.debian.org/viewvc/pkg-libburnia?view=revision&revision=299 > * Bug Fix > - fix-bug-cdrskin_timestamp.h. What's this ? Let's discuss upstream. > - New release closes bug libburn/sector.c (Closes: #690207, #246647). #246647 is a cdrecord bug. Unrelated to libburn. > - Only more information, don't have bug (Closes: #702621) This is a drive-media problem which the burn program cannot fix. Have anice day :) Thomas
