On 12/11/2016 02:02 PM, Alessandro Vesely wrote:
> On Sun 11/Dec/2016 12:51:00 +0100 Stefan Hornburg (Racke) wrote:
>> On 12/11/2016 03:12 AM, Mark Constable wrote:
>>> On 11/12/16 03:09, SZÉPE Viktor wrote:
>>>> On 07/12/16 00:04, Ondřej Surý wrote:
>>>>>
>>>>> I intend to properly orphan the packages before stretch release and
>>>>> remove them from next Debian stable release. Well, unless somebody
>>>>> comes up and makes a hard promise to take care of all Courier MTA till
>>>>> Debian stretch (next stable) end-of-life and becomes maintainers.
>>>
>>> This was one of the saddest emails I have ever received.
>>>
>>> If my servers ran Archlinux I'd have no problem building from source,
>>> and even maintaining a source package in AUR, but even though I am a
>>> staunch ubuntu-server user I really don't like debs (or rpm) packaging.
> 
> Aha, that implies you know them somewhat...
> 
>>> I have little choice left but to start testing postfix/dovecot :-(
>>>
>>> And so far I really despise what I see after becoming so comfortable
>>> with courier. No SNI (SSL on a single IP) for a start and goodness
>>> knows what else will be awkward to impossible to achieve compared to
>>> the relative ease and unified sanity of the courier suite.
>>>
>>> And not least of all the superb effort put in by Sam, and others, on
>>> this list to provide a level of consistent free support rarely seen
>>> elsewhere (in my experience.)
>>>
>>>> I could lend a hand to the maintainer for couple of hours/month. I
>>>> am Courier user <snip>
> 
> +1  Although I use Debian (but not systemd) I always compiled Courier from 
> sources, so I know very little of Courier's Debian-specific stuff.
> 
>>>> Though I've never used Debian's source/build infrastructure.
> 
> Ditto, almost.
> 
>>> That's very encouraging. I am less experienced with Debian packaging than
>>> you so I'm not sure I can do much to help. It looks like ra...@linuxia.de
>>> has retired from the original Debian packages and Ondřej put in an amazing
>>> effort to re-package the latest source to run under the "courier" user
>>> instead of the previous "daemon" user (more in line with original source).
>>
>> Yeah I had too little time to continue with maintaining such a large package
>> on my own. I certainly appreciate Ondřej's support and I could help out
>> with the Debian specifics of this package.
> 
> I'm not clear whether Ondřej's changes break compatibility with the current 
> package.  If aiming at an incompatible repackaging, dropping the existing 
> packages and creating new ones can be easier.  Call it /renaming/ if you like.
> 
> Pros.  Renaming makes it clear that some work is needed to migrate to the new 
> packages.  Custom scripts will have to be reviewed, for example.  Bugs don't 
> need to be migrated, perhaps.
> 
> Cons.  Sense of discontinuity.  Panic?
> 
>>> Some discussion on ubuntu-devel-disc...@lists.ubuntu.com might dig up some
>>> more support and help determine if Ondřejs' packages could replace the
>>> current way-to-old barely-on-life-support package set.
> 
> I propose interested Ubuntu users subscribe here.  I reckon subscribers of 
> this 
> list, even if not interested in Debian packaging, are more likely to 
> occasionally lend some interest on the subject than subscribers of Ububtu- or 
> Debian- devel who are not interested in Courier or mail.  Am I wrong?
> 
>>>> Two things:
>>>> The package has no git source https://packages.qa.debian.org/c/courier.html
>>>> Courier upstream has no bug-tracking system.
>>>>
>>>> I would choose GitHub as a place to store /debian and to communicate
>>>> with upstream.
>>>
>>> Unfortunately Sam doesn't seem interested in moving his whole development
>>> system over to Github.
>>
>> We could also use the existing Git infrastructure of Debian for the packaging
>> files (https://wiki.debian.org/PackagingWithGit).
> 
> Is that the "Importing upstream as tarballs" thing?
> 

Amongst other things, yes.

Regards
          Racke

> Ale
> 
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today.http://sdm.link/xeonphi
> _______________________________________________
> courier-users mailing list
> courier-users@lists.sourceforge.net
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
> 


-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration.

------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/xeonphi
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to