Debian stable users will start reporting bugs for really old releases of
vdirsyncer on my issue tracker. And while Debian's documentation may have
made this situation extremely clear, apparently nobody reads it. This is
already happening with other software.
Hmm. That is very inconsiderate of
On Tue, Apr 05, 2016 at 03:08:44PM -0500, Stephen Paul Weber wrote:
> To be clear: this is only true if you are the Debian maintainer for
> vdirsyncer. If someone else is the maintainer (as, reading this thread, it
> seems is the intent) then it is *their* job to backport any relevant bugfixes
> a
I suspect that if vdirsyncer makes its way into stable before 1.0, it
essentially means I'm forced into long-term support of whichever release is in
stable. However, ideally I'd like to only support the latest release of
vdirsyncer.
To be clear: this is only true if you are the Debian maintainer
(forgot to CC the Debian bugtracker)
--- Begin Message ---
On Thu, Mar 31, 2016 at 02:19:48PM +0200, Enrico Zini wrote:
> On Tue, Feb 02, 2016 at 06:07:56PM +0100, Markus Unterwaditzer wrote:
> > > Sorry to insist, but I'd really like to have a definitive answer on this
> > > before
> > vdirsyncer
On Tue, Feb 02, 2016 at 06:07:56PM +0100, Markus Unterwaditzer wrote:
> Sorry to insist, but I'd really like to have a definitive answer on this
> before
> vdirsyncer is packaged.
>
> I suspect that if vdirsyncer makes its way into stable before 1.0, it
> essentially means I'm forced into long-t
Sorry to insist, but I'd really like to have a definitive answer on this before
vdirsyncer is packaged.
I suspect that if vdirsyncer makes its way into stable before 1.0, it
essentially means I'm forced into long-term support of whichever release is in
stable. However, ideally I'd like to only sup
I am pretty new to maintaining official Debian packages but if new
release won't introduce some new dependencies (especially that are not
packaged yet), creating new package version should be almost automatic.
Of course there's some unstable -> testing -> stable release process,
but unfortunately
A question: If I release an update of vdirsyncer the day after it is packaged
for Debian, how long would it take to reach the repo? Which intermediate
staging repos are there that would delay an immediate update of the package?
On 29 January 2016 17:05:18 CET, Filip Pytloun wrote:
>Hello,
>
>I'
Hello,
I've almost finished packaging of vdirsyncer but it requires
dependencies not currently in sid:
python-click-log and python-atomicwrites
It shouldn't be difficult to package these as well, but any help is
welcome :-)
Filip
signature.asc
Description: Digital signature
9 matches
Mail list logo
