[Olsr-dev] patches from Debian package WAS: Debian/Ubuntu package updates

[Ferry Huberts]

On 02/04/13 23:23, Hans-Christoph Steiner wrote:
> 
> I'm moving this to olsr-dev since its become a dev conversation:
> 
> Here are the remaining patches:
> http://anonscm.debian.org/viewvc/collab-maint/deb-maint/olsrd/trunk/debian/patches/
> 
> I see no point in maintaining the Debian-specific patches in the olsr git.
> Those patches are to force olsrd into Debian policy, things like using
> /etc/olsrd/ and /usr/lib/olsrd, turning of the src/builddata.c generation hack
> since that's handled in the packaging tools, etc:
> 
> 110-build_fix.patch

we don't want this one

> 290-hardcode-etc-olsrd-olsrd-conf.patch

please submit on the ML so that we can discuss it

> 
> Two other patches, I have no idea how they should be handled, they were there
> when I started working on the package:
> 
> 111-build-mips-and-armhf.patch

please submit on the ML so that we can discuss it

> 260-quagga-plugin-detect-protocol-version.patch

please submit on the ML so that we can discuss it

> 
> The last patch includes the last of the Debian hardening flags that have not
> been included yet. It makes sense to me to include those upstream if it makes
> sense on all of the supported platforms.  Or someone would have to figure out
> how to make it apply to only the platforms that should have it:
> 
> 310-hardening-fixes.patch
> 

please submit on the ML so that we can discuss it

> .hc
> 
> 
>  I
> On 04/02/2013 11:23 AM, Henning Rogge wrote:
>> Hi,
>>
>> do you think it would be feasible (maybe for the 0.6.5.2 upload) to
>> create a "v0.6.5.2_debian" branch where you commit all the patches
>> that got uploaded into the Debian release?
>>
>> That would make it easier for us to help Debian users, because we can
>> quickly see what code they are running.
>>
>> Henning
>>
>> On Tue, Apr 2, 2013 at 8:18 PM, Hans-Christoph Steiner
>> <(spam-protected)> wrote:
>>>
>>> For basically any sizeable distro, there is a 'stable' release and a 'current'
>>> release.
>>>
>>> For squeeze/stable, only security or total breakage bugs can be fixed, and
>>> only with very targetted patches.  That's basically the same with
>>> wheezy/testing, since its about to be released.  For unstable, I can put
>>> whatever version in, and that will also be included in the upcoming Ubuntu
>>> release.  experimental can have anything, and nothing relies on it.
>>>
>>> I uploaded 0.6.3-6 to unstable so it gets included in Ubuntu/raring.  Its very
>>> well tested at this point.  Once 0.6.5.2 gets more testing, I'll push it to
>>> unstable.
>>>
>>> .hc
>>>
>>> On 04/02/2013 12:34 AM, Ferry Huberts wrote:
>>>>
>>>>
>>>> On 02/04/13 08:17, Hans-Christoph Steiner wrote:
>>>>>
>>>>> Just pushed a bunch of package updates, here's how things stand now:
>>>>>
>>>>> Debian:
>>>>> http://packages.debian.org/search?keywords=olsrd
>>>>> * wheezy: 0.6.2 with the net_output stack fix from 0.6.4
>>>>> * squeeze-backports: the wheezy version above
>>>>> * unstable: 0.6.3 with the net_output stack fix from 0.6.4
>>>>> * experimental: 0.6.5.2 with some hardening flags
>>>>>
>>>>> Ubuntu: same as Debian/unstable
>>>>> https://launchpad.net/~guardianproject/+archive/commotion/+packages
>>>>>
>>>>> Any testing, feedback, etc. is most appreciated!
>>>>>
>>>>
>>>>
>>>> Why not straight from the release branch for all?
>>>> (0.6.5.2 + the 4 patches at the time of writing)
>>>>
>>>> We're doing the maintenance on the release branch especially for
>>>> distributions. If they're not using that then there's no point in us
>>>> doing that, IMHO.
>>>>
>>>>
>>>
>>> --
>>> Olsr-users mailing list
>>> (spam-protected)
>>> https://lists.olsr.org/mailman/listinfo/olsr-users
>>
>>
>>

-- 
Ferry Huberts