On Sun, Mar 21, 2010 at 01:08:28AM -0000, Steve Langasek wrote: > Apparently we're having a communication problem here. The information > you need to provide for a freeze exception are: > > * A description of the proposed changes, with sufficient detail to > estimate their potential impact on the distribution > * A rationale for the exception, explaining the benefit of the change > * Any additional information which would be helpful in considering the > decision > > Sending more logs doesn't answer these points. Is there an upstream > changelog describing the differences in the sl-modem package? That > would be a starting point. ---end quoted text---
Ok, I thought the changes meant the debian changelog. There is no upstream changelog, but the upstream changes are the following: 1] Applying some of the Debian patches that were in 2.9.11~20080817-3 (the list of applied patches is in patches/sldiffs-20090222/ folder in upstream tarball) 2] Adding a patch to fix FTBFS with linux kernels >= 2.6.32 3] Adding a patch to fix NO CARRIER issue with linux kernels >= 2.6.31, that patch fixes a bug that made sl-modem not usable at all on karmic. As for the rationale for the exception: I did mention the bugs on Launchpad that it closes. Is there something else I should add ? -- أحمد المحمودي (Ahmed El-Mahmoudy) Digital design engineer GPG KeyID: 0xEDDDA1B7 GPG Fingerprint: 8206 A196 2084 7E6D 0DF8 B176 BC19 6A94 EDDD A1B7 -- Sync sl-modem 2.9.11~20100303-2 (restricted) from Debian unstable (non-free) https://bugs.launchpad.net/bugs/402874 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
