Re: interested in (co-)maintaining midori

2015-09-13 Thread Sergio Durigan Junior 
On Wednesday, September 09 2015, I wrote:

> On Monday, August 24 2015, I wrote:
>
>> On Friday, August 14 2015, Andres Salomon wrote:
>>
 Your work was done back in June, so if you prefer I can provide
 patches against your branch to implement/fix the issues I have been
 working on. It won't really matter much, I think: in the end, we'll
 have to use the "official" repository anyway and patch it.
 
>>>
>>> That would be highly preferred, simply for reviewing purposes.  I'm
>>> also happy to rewrite parts of my history to, for example, not include
>>> the -O--buildsystem stuff.  But the existing git history is useful, and
>>> I'd rather work from that.
>>
>> OK, I've done it:
>>
>>   
>>
>> It's the same link, but the repository is a new one, based on the
>> official repository.
>
> Just another update.
>
> I've re-created the repository above (the previous version contained
> some mistakes, and I thought it made sense to restart from scratch).
> Now, you can find the latest version of Midori (0.5.11, released a few
> days ago) along with all the other changes that I had already made.
>
> Still builds successfully, and I'm using this latest version without
> problems.  IOW, everything is ready to be used in Debian, and I'm pretty
> happy with the current state of the repository.

One (last?) update.

I have upgrade/recreated the repository one more time now.  Thadeu
Cascardo pointed me to two lintian warnings that I had not seen before
(they're fixed now), and I've cherry-picked Andreas's commits (those
that import the NMU-0.2 and merge it to master), so now I think
everything is *really* covered.  Oh, and I've searched the BTS and found
two bugs that requested a new version to be packaged, so I'm closing
them in the changelog.  I intend to do a full bug triage once the
package is back to life.

Just for the record, I've kept *all* history from the previous git
branches, so absolutely nothing is deleted nor lost.

In other words, the package is ready to be re-uploaded.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: interested in (co-)maintaining midori

2015-09-13 Thread Andres Salomon 
On Sun, 13 Sep 2015 20:33:52 -0400
Sergio Durigan Junior  wrote:

> On Wednesday, September 09 2015, I wrote:
> 
> > On Monday, August 24 2015, I wrote:
> >
> >> On Friday, August 14 2015, Andres Salomon wrote:
> >>
>  Your work was done back in June, so if you prefer I can provide
>  patches against your branch to implement/fix the issues I have
>  been working on. It won't really matter much, I think: in the
>  end, we'll have to use the "official" repository anyway and
>  patch it.
>  
> >>>
> >>> That would be highly preferred, simply for reviewing purposes.
> >>> I'm also happy to rewrite parts of my history to, for example,
> >>> not include the -O--buildsystem stuff.  But the existing git
> >>> history is useful, and I'd rather work from that.
> >>
> >> OK, I've done it:
> >>
> >>   
> >>
> >> It's the same link, but the repository is a new one, based on the
> >> official repository.
> >
> > Just another update.
> >
> > I've re-created the repository above (the previous version contained
> > some mistakes, and I thought it made sense to restart from scratch).
> > Now, you can find the latest version of Midori (0.5.11, released a
> > few days ago) along with all the other changes that I had already
> > made.
> >
> > Still builds successfully, and I'm using this latest version without
> > problems.  IOW, everything is ready to be used in Debian, and I'm
> > pretty happy with the current state of the repository.
> 
> One (last?) update.
> 
> I have upgrade/recreated the repository one more time now.  Thadeu
> Cascardo pointed me to two lintian warnings that I had not seen before
> (they're fixed now), and I've cherry-picked Andreas's commits (those
> that import the NMU-0.2 and merge it to master), so now I think
> everything is *really* covered.  Oh, and I've searched the BTS and
> found two bugs that requested a new version to be packaged, so I'm
> closing them in the changelog.  I intend to do a full bug triage once
> the package is back to life.
> 
> Just for the record, I've kept *all* history from the previous git
> branches, so absolutely nothing is deleted nor lost.
> 
> In other words, the package is ready to be re-uploaded.
> 
> Thanks,
> 

Fantastic, thank you!  I'd say go ahead and upload it.  I won't have
time to review it; school teachers here are on strike combined w/
work deadlines mean I lack any free time right now.  I'll check out
your work once my kid's back in school again.

I look forward to grabbing the latest midori from sid.

Re: interested in (co-)maintaining midori

2015-09-13 Thread Thadeu Lima de Souza Cascardo 
On September 13, 2015 9:33:52 PM GMT-03:00, Sergio Durigan Junior 
 wrote:
>On Wednesday, September 09 2015, I wrote:
>
>> On Monday, August 24 2015, I wrote:
>>
>>> On Friday, August 14 2015, Andres Salomon wrote:
>>>
> Your work was done back in June, so if you prefer I can provide
> patches against your branch to implement/fix the issues I have
>been
> working on. It won't really matter much, I think: in the end,
>we'll
> have to use the "official" repository anyway and patch it.
> 

 That would be highly preferred, simply for reviewing purposes.  I'm
 also happy to rewrite parts of my history to, for example, not
>include
 the -O--buildsystem stuff.  But the existing git history is useful,
>and
 I'd rather work from that.
>>>
>>> OK, I've done it:
>>>
>>>   
>>>
>>> It's the same link, but the repository is a new one, based on the
>>> official repository.
>>
>> Just another update.
>>
>> I've re-created the repository above (the previous version contained
>> some mistakes, and I thought it made sense to restart from scratch).
>> Now, you can find the latest version of Midori (0.5.11, released a
>few
>> days ago) along with all the other changes that I had already made.
>>
>> Still builds successfully, and I'm using this latest version without
>> problems.  IOW, everything is ready to be used in Debian, and I'm
>pretty
>> happy with the current state of the repository.
>
>One (last?) update.
>
>I have upgrade/recreated the repository one more time now.  Thadeu
>Cascardo pointed me to two lintian warnings that I had not seen before
>(they're fixed now), and I've cherry-picked Andreas's commits (those
>that import the NMU-0.2 and merge it to master), so now I think
>everything is *really* covered.  Oh, and I've searched the BTS and
>found
>two bugs that requested a new version to be packaged, so I'm closing
>them in the changelog.  I intend to do a full bug triage once the
>package is back to life.
>
>Just for the record, I've kept *all* history from the previous git
>branches, so absolutely nothing is deleted nor lost.
>
>In other words, the package is ready to be re-uploaded.
>
>Thanks,

Thanks, Sergio.

I find the repo and package in a good state for an upload. I will do it 
tomorrow night, if there are no further strong objections.

Thanks Andres for his work as well, and all the others for their past 
contributions.

Cascardo.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: interested in (co-)maintaining midori

2015-09-13 Thread Sergio Durigan Junior 
On Sunday, September 13 2015, Andres Salomon wrote:

>> One (last?) update.
>> 
>> I have upgrade/recreated the repository one more time now.  Thadeu
>> Cascardo pointed me to two lintian warnings that I had not seen before
>> (they're fixed now), and I've cherry-picked Andreas's commits (those
>> that import the NMU-0.2 and merge it to master), so now I think
>> everything is *really* covered.  Oh, and I've searched the BTS and
>> found two bugs that requested a new version to be packaged, so I'm
>> closing them in the changelog.  I intend to do a full bug triage once
>> the package is back to life.
>> 
>> Just for the record, I've kept *all* history from the previous git
>> branches, so absolutely nothing is deleted nor lost.
>> 
>> In other words, the package is ready to be re-uploaded.
>> 
>> Thanks,
>> 
>
> Fantastic, thank you!  I'd say go ahead and upload it.  I won't have
> time to review it; school teachers here are on strike combined w/
> work deadlines mean I lack any free time right now.  I'll check out
> your work once my kid's back in school again.

Thank you for your previous work, too.  I would probably have missed the
NMU if it weren't your repository.

> I look forward to grabbing the latest midori from sid.

Neat.  Please let me know if you notice anything worth mentioning.

Good luck with your deadlines,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: interested in (co-)maintaining midori

2015-09-08 Thread Sergio Durigan Junior 
On Monday, August 24 2015, I wrote:

> On Friday, August 14 2015, Andres Salomon wrote:
>
>>> Your work was done back in June, so if you prefer I can provide
>>> patches against your branch to implement/fix the issues I have been
>>> working on. It won't really matter much, I think: in the end, we'll
>>> have to use the "official" repository anyway and patch it.
>>> 
>>
>> That would be highly preferred, simply for reviewing purposes.  I'm
>> also happy to rewrite parts of my history to, for example, not include
>> the -O--buildsystem stuff.  But the existing git history is useful, and
>> I'd rather work from that.
>
> OK, I've done it:
>
>   
>
> It's the same link, but the repository is a new one, based on the
> official repository.

Just another update.

I've re-created the repository above (the previous version contained
some mistakes, and I thought it made sense to restart from scratch).
Now, you can find the latest version of Midori (0.5.11, released a few
days ago) along with all the other changes that I had already made.

Still builds successfully, and I'm using this latest version without
problems.  IOW, everything is ready to be used in Debian, and I'm pretty
happy with the current state of the repository.

Andreas, what do you think if we push my changes to the official
repository and start working from there?  It has been a while since
we're discussing without reaching a real agreement, and Midori is still
not present in testing.

Meanwhile, I have been looking at the BTS and making a list of bugs that
should be fixed by this update.

Comments are welcome.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: interested in (co-)maintaining midori

2015-08-24 Thread Sergio Durigan Junior 
On Friday, August 14 2015, Andres Salomon wrote:

 Your work was done back in June, so if you prefer I can provide
 patches against your branch to implement/fix the issues I have been
 working on. It won't really matter much, I think: in the end, we'll
 have to use the official repository anyway and patch it.
 

 That would be highly preferred, simply for reviewing purposes.  I'm
 also happy to rewrite parts of my history to, for example, not include
 the -O--buildsystem stuff.  But the existing git history is useful, and
 I'd rather work from that.

OK, I've done it:

  http://git.sergiodj.net/?p=debian/midori.git;a=summary

It's the same link, but the repository is a new one, based on the
official repository.

I tried to make my commits more granular, but there's a limit for that.
The first commit is the biggest one, but they should all be
self-explanatory (along with their commit messages).

The package builds successfully here, without any lintian warnings (I've
had to silence a bunch of them; I'll contact the lintian maintainers
later to do a case-by-case analysis).  I have also renamed some stuff,
like the conf/*.h files, and deleted others.

Comments are welcome, of course.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: interested in (co-)maintaining midori

2015-08-14 Thread Yves-Alexis Perez 
On ven., 2015-08-14 at 02:39 -0400, Sergio Durigan Junior wrote:
 Did you guys have time to look at my repository?

I'm not right sure who you're asking exactly, but just to re-state this
again: I don't want to be involved with Midori packaging anymore *at
all*. You can safely drop me from those mails, and do whatever you
want, I won't bother at all.

Regards,
-- 
Yves-Alexis


signature.asc
Description: This is a digitally signed message part

Re: interested in (co-)maintaining midori

2015-08-14 Thread Andres Salomon 
On Fri, 14 Aug 2015 14:09:46 -0400
Sergio Durigan Junior sergi...@sergiodj.net wrote:

 On Friday, August 14 2015, Andres Salomon wrote:
 
  On Fri, 14 Aug 2015 02:39:08 -0400
  Sergio Durigan Junior sergi...@sergiodj.net wrote:
 
  On Saturday, August 08 2015, I wrote:
  
   I'll take a look at your branch once it's published.
  
   Thanks.  I have just published it:
  
 http://git.sergiodj.net/?p=debian/midori.git;a=summary
  
   This is *not* based on the official repository, but that's just
   because I found it more convenient.  As I said above, I intend to
   merge it to the original repository very soon.
  
  Hello,
  
  Did you guys have time to look at my repository?  I have just
  pushed a few more changes.  In fact, I might as well incorporate
  my changes into the official repository, and make it ready to be
  used if needed. Unfortunately I have been working on this during
  my spare time, which has been very little lately, so I'm not
  progressing as fast as I wished.  Nevertheless, things are almost
  ready; I would just like to make a few adjustments.
 
  Yes, I took a look.  I still don't understand why you're starting
  from scratch.
 
 Hi Andres,
 
 As I explained in my previous message, starting from scratch is not
 really true in this case; I shouldn't have used this expression,
 sorry. What I am doing is cleaning things up and try to come up with
 a nicer package than what we have now.  But as you can see, I have
 also used many pieces of the old package.

Yes, I understand, but doing it this way makes it much harder for me to
review your work (which is why I waited a week to give it more
than a cursory glance, since it's currently one huge patch).

 
   I also don't understand why you didn't look at my work, which
  was done back in June (yours appears to be committed in August?),
  and calls debhelper with things like:
 
  dh_auto_install -O--buildsystem=cmake
 
  http://lunge.queued.net/gitweb/?p=midori;a=commitdiff;h=f47a9488f9a26b8e751a25368def76bca7f33c0b
 
 I looked at your work.  I thought I had mentioned that.
 
 First, I don't see the need to override some rules just to pass
 -O--buildsystem=cmake; debhelper is smart enough to figure that out,
 it seems.  I am not using this extra flag and things are working
 totally fine for me.

Cool, I'll try that out.

 
 A second thing is that your work still contains old stuff that could
 be removed/tweaked.  For example, I noticed that the original shlibs
 file contains wrong entries when you build the new package; that's
 why I had to override it with a hand-made one (as well as provide a
 lintian-override file to silence warnings because of the unused
 shlibs, which are actually Midori plugins).
 

Right.  I'm not claiming my work was complete; just that it works and
is based on the old git repo.


 Your work was done back in June, so if you prefer I can provide
 patches against your branch to implement/fix the issues I have been
 working on. It won't really matter much, I think: in the end, we'll
 have to use the official repository anyway and patch it.
 

That would be highly preferred, simply for reviewing purposes.  I'm
also happy to rewrite parts of my history to, for example, not include
the -O--buildsystem stuff.  But the existing git history is useful, and
I'd rather work from that.

Thanks!

Re: interested in (co-)maintaining midori

2015-08-14 Thread Sergio Durigan Junior 
On Saturday, August 08 2015, I wrote:

 I'll take a look at your branch once it's published.

 Thanks.  I have just published it:

   http://git.sergiodj.net/?p=debian/midori.git;a=summary

 This is *not* based on the official repository, but that's just because
 I found it more convenient.  As I said above, I intend to merge it to
 the original repository very soon.

Hello,

Did you guys have time to look at my repository?  I have just pushed a
few more changes.  In fact, I might as well incorporate my changes into
the official repository, and make it ready to be used if needed.
Unfortunately I have been working on this during my spare time, which
has been very little lately, so I'm not progressing as fast as I
wished.  Nevertheless, things are almost ready; I would just like to
make a few adjustments.

Andres, have you thought about my proposal of creating a group for
packaging Midori?  Can I go ahead and request this group on Alioth?

Comments about the current state of the repository are welcome, of
course.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: interested in (co-)maintaining midori

2015-08-14 Thread Andres Salomon 
On Fri, 14 Aug 2015 02:39:08 -0400
Sergio Durigan Junior sergi...@sergiodj.net wrote:

 On Saturday, August 08 2015, I wrote:
 
  I'll take a look at your branch once it's published.
 
  Thanks.  I have just published it:
 
http://git.sergiodj.net/?p=debian/midori.git;a=summary
 
  This is *not* based on the official repository, but that's just
  because I found it more convenient.  As I said above, I intend to
  merge it to the original repository very soon.
 
 Hello,
 
 Did you guys have time to look at my repository?  I have just pushed a
 few more changes.  In fact, I might as well incorporate my changes
 into the official repository, and make it ready to be used if needed.
 Unfortunately I have been working on this during my spare time, which
 has been very little lately, so I'm not progressing as fast as I
 wished.  Nevertheless, things are almost ready; I would just like to
 make a few adjustments.

Yes, I took a look.  I still don't understand why you're starting from
scratch.  I also don't understand why you didn't look at my work, which
was done back in June (yours appears to be committed in August?), and
calls debhelper with things like:

dh_auto_install -O--buildsystem=cmake

http://lunge.queued.net/gitweb/?p=midori;a=commitdiff;h=f47a9488f9a26b8e751a25368def76bca7f33c0b


 
 Andres, have you thought about my proposal of creating a group for
 packaging Midori?  Can I go ahead and request this group on Alioth?
 
 Comments about the current state of the repository are welcome, of
 course.
 
 Cheers,

Re: interested in (co-)maintaining midori

2015-08-14 Thread Sergio Durigan Junior 
On Friday, August 14 2015, Andres Salomon wrote:

 On Fri, 14 Aug 2015 02:39:08 -0400
 Sergio Durigan Junior sergi...@sergiodj.net wrote:

 On Saturday, August 08 2015, I wrote:
 
  I'll take a look at your branch once it's published.
 
  Thanks.  I have just published it:
 
http://git.sergiodj.net/?p=debian/midori.git;a=summary
 
  This is *not* based on the official repository, but that's just
  because I found it more convenient.  As I said above, I intend to
  merge it to the original repository very soon.
 
 Hello,
 
 Did you guys have time to look at my repository?  I have just pushed a
 few more changes.  In fact, I might as well incorporate my changes
 into the official repository, and make it ready to be used if needed.
 Unfortunately I have been working on this during my spare time, which
 has been very little lately, so I'm not progressing as fast as I
 wished.  Nevertheless, things are almost ready; I would just like to
 make a few adjustments.

 Yes, I took a look.  I still don't understand why you're starting from
 scratch.

Hi Andres,

As I explained in my previous message, starting from scratch is not
really true in this case; I shouldn't have used this expression, sorry.
What I am doing is cleaning things up and try to come up with a nicer
package than what we have now.  But as you can see, I have also used
many pieces of the old package.

  I also don't understand why you didn't look at my work, which
 was done back in June (yours appears to be committed in August?), and
 calls debhelper with things like:

 dh_auto_install -O--buildsystem=cmake

 http://lunge.queued.net/gitweb/?p=midori;a=commitdiff;h=f47a9488f9a26b8e751a25368def76bca7f33c0b

I looked at your work.  I thought I had mentioned that.

First, I don't see the need to override some rules just to pass
-O--buildsystem=cmake; debhelper is smart enough to figure that out,
it seems.  I am not using this extra flag and things are working totally
fine for me.

A second thing is that your work still contains old stuff that could be
removed/tweaked.  For example, I noticed that the original shlibs file
contains wrong entries when you build the new package; that's why I had
to override it with a hand-made one (as well as provide a
lintian-override file to silence warnings because of the unused
shlibs, which are actually Midori plugins).

Your work was done back in June, so if you prefer I can provide patches
against your branch to implement/fix the issues I have been working on.
It won't really matter much, I think: in the end, we'll have to use the
official repository anyway and patch it.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

Re: interested in (co-)maintaining midori

2015-08-08 Thread Andres Salomon 
On Fri, 07 Aug 2015 15:39:54 -0400
Sergio Durigan Junior sergi...@sergiodj.net wrote:

 On Saturday, August 01 2015, Andres Salomon wrote:
 
  I'm interested in helping out with Midori packaging.  I'm not sure
  who's still interested in the package at this point (I know Corsac
  isn't, so I didn't Cc him).  I've created a git branch for the
  0.5.10 release here:
  
  git://lunge.queued.net/git/midori
  http://lunge.queued.net/gitweb/?p=midori;a=shortlog;h=refs/heads/0.5.10
  
  It builds (on sid and jessie) and runs (on jessie) for me, though
  it definitely needs more work tightening up deps, cleaning up
  lintian errors, etc.
  
  I'm happy to co-maintain the package, or take it over; whatever
  folks prefer.  Please let me know what I should do, since it was
  never formally orphaned.
 
 
  I haven't heard anything regarding this, and it's been over a month.
  Should I just clean up my midori packages and upload?  If I don't
  hear anything back and there's no activity with the package, that's
  my plan.
 
 Hi Andres,
 
 I saw your message only yesterday, sorry about that.  As it turns
 out, I have also been working on getting Midori fixed.  My intention
 is to maintain it; Thadeu Cascardo is going to help me take over the
 package. However, as you are also willing to co-maintain the package,
 maybe we could create a group on Alioth to work together?

There's already a midori packaging group/git repo:

http://anonscm.debian.org/cgit/collab-maint/midori.git/

My repo is based on this, and my plan was to get access permission
from Corsac after uploading the package to sid.  Then I could push
my changes, maintaining history.  That would be my preference.

 
 I also looked at your branch.  What I am doing is basically a
 repackaging, from scratch, trying to figure out what's important and
 what's not.  I'll publish my branch later today.

Why from scratch?

I'll take a look at your branch once it's published.

 
 So, any opinions on how to proceed?
 
 Thanks,
 


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150807225117.4a586...@e7240.queued.net

Re: interested in (co-)maintaining midori

2015-08-08 Thread Sergio Durigan Junior 
On Saturday, August 08 2015, Andres Salomon wrote:

 I saw your message only yesterday, sorry about that.  As it turns
 out, I have also been working on getting Midori fixed.  My intention
 is to maintain it; Thadeu Cascardo is going to help me take over the
 package. However, as you are also willing to co-maintain the package,
 maybe we could create a group on Alioth to work together?

 There's already a midori packaging group/git repo:

 http://anonscm.debian.org/cgit/collab-maint/midori.git/

Hello Andres,

Yes, I know that.  I have been using this repository as the base, too.
But the idea is to get a real group for Midori, like the Mozilla
packagers have (for example).  This git repository is just this: a git
repository.  With a group we would have the advantage of having an
official mailing list to coordinate efforts, and also interested
(co-)maintainers for the package working together.

 My repo is based on this, and my plan was to get access permission
 from Corsac after uploading the package to sid.  Then I could push
 my changes, maintaining history.  That would be my preference.

Sure, I certainly don't want to throw away any existing changes...

 I also looked at your branch.  What I am doing is basically a
 repackaging, from scratch, trying to figure out what's important and
 what's not.  I'll publish my branch later today.

 Why from scratch?

... and maybe I should have been more clear about the from scratch
part.  It was just a stronger way of saying that I am actually reviewing
every file under debian/ to see if everything is really needed or not.

What I noticed from your branch is that you don't really delete the old
stuff; you are mostly making sure that the latest version works.  I am
spending time removing unnecessary things and figuring out how to
optimize other things there.  My intention is to get the package in good
shape again (but not take too long doing that, of course).

 I'll take a look at your branch once it's published.

Thanks.  I have just published it:

  http://git.sergiodj.net/?p=debian/midori.git;a=summary

This is *not* based on the official repository, but that's just because
I found it more convenient.  As I said above, I intend to merge it to
the original repository very soon.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87twsajnm3@sergiodj.net

Re: interested in (co-)maintaining midori

2015-08-07 Thread Sergio Durigan Junior 
On Saturday, August 01 2015, Andres Salomon wrote:

 I'm interested in helping out with Midori packaging.  I'm not sure
 who's still interested in the package at this point (I know Corsac
 isn't, so I didn't Cc him).  I've created a git branch for the 0.5.10
 release here:
 
 git://lunge.queued.net/git/midori
 http://lunge.queued.net/gitweb/?p=midori;a=shortlog;h=refs/heads/0.5.10
 
 It builds (on sid and jessie) and runs (on jessie) for me, though it
 definitely needs more work tightening up deps, cleaning up lintian
 errors, etc.
 
 I'm happy to co-maintain the package, or take it over; whatever folks
 prefer.  Please let me know what I should do, since it was never
 formally orphaned.


 I haven't heard anything regarding this, and it's been over a month.
 Should I just clean up my midori packages and upload?  If I don't hear
 anything back and there's no activity with the package, that's my
 plan.

Hi Andres,

I saw your message only yesterday, sorry about that.  As it turns out, I
have also been working on getting Midori fixed.  My intention is to
maintain it; Thadeu Cascardo is going to help me take over the package.
However, as you are also willing to co-maintain the package, maybe we
could create a group on Alioth to work together?

I also looked at your branch.  What I am doing is basically a
repackaging, from scratch, trying to figure out what's important and
what's not.  I'll publish my branch later today.

So, any opinions on how to proceed?

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/8737zulwfp@sergiodj.net

Re: interested in (co-)maintaining midori

2015-08-01 Thread Andres Salomon 
On Sun, 28 Jun 2015 05:17:01 -0700
Andres Salomon dilin...@queued.net wrote:

 Hi,
 
 I'm interested in helping out with Midori packaging.  I'm not sure
 who's still interested in the package at this point (I know Corsac
 isn't, so I didn't Cc him).  I've created a git branch for the 0.5.10
 release here:
 
 git://lunge.queued.net/git/midori
 http://lunge.queued.net/gitweb/?p=midori;a=shortlog;h=refs/heads/0.5.10
 
 It builds (on sid and jessie) and runs (on jessie) for me, though it
 definitely needs more work tightening up deps, cleaning up lintian
 errors, etc.
 
 I'm happy to co-maintain the package, or take it over; whatever folks
 prefer.  Please let me know what I should do, since it was never
 formally orphaned.


I haven't heard anything regarding this, and it's been over a month.
Should I just clean up my midori packages and upload?  If I don't hear
anything back and there's no activity with the package, that's my
plan.

[d-d, please Cc me on responses; I'm not subscribed to the list]


-- 
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150801135002.2f310...@e7240.queued.net