Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Tue, 8 Jul 2014 11:00:34 +0400
From: "(GalaxyMaster)" <>
Subject: recent updates


I see that you've started to updated packages.  This makes my life a bit
harder since I need to double-check and correct my patches.  For
example, I had an update to gnupg and now I need to compare that
cumulative patch from ALT with all patches I have in my package in
order to see whether there is something missing or not.  This is not
that important but adds some workload where it could have been avoided.

As of beginning of July my first batch of changes to Owl was compiling
flawlessly (under 10 iterations of 'make buildworld' to bring the system
to a state where everything is updated).

Another problem is that I performed extensive tests on rebuilding the
whole Owl userland with my updated packages.  Now, these updates render
my tests obsolete since I need to rebuild everything again just to
ensure that whatever has been changed is not broken by my updates. :(

I wish you've spent this time to branch Owl as we discussed, so I could
commit my part.  You could just have said that you need gnupg updated
and it would have been done instantly (since my goal was to do updates
of the userland and I clearly allocated time for this).

I still have a week to commit and fix whatever breaks as the result, but
then I'll be likely unavailable for several months.  It's just a bit sad
that I've spent almost 2 months to make this update and I cannot commit.
Moreover, I'm afraid if I do not commit it soon we will just lose it.


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.