On 05.07.22 17:14, Boyuan Yang wrote:
Source: dvcs-autosync
Version: 0.5+nmu1
Severity: important
Tags: sid
X-Debbugs-CC: rm...@debian.org
Dear Debian dvcs-autosync package maintainer,
I checked the condition of package dvcs-autosync in Debian
at https://tracker.debian.org/pkg/dvcs-autosync , a
Hi Moritz,
The state on Github is unfortunately incomplete, as I got stuck in the
process of converting to Python 3. The problem is that the XMPP library
I used before hasn't been ported to Python 3 and I would either need to
change to a different XMPP support or to another protocol - considering
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-12-13 02:33, Mattia Rizzolo wrote:
> I've prepared an NMU for dvcs-autosync (versioned as 0.5+nmu1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
Feel free to NMU - I have no other patches that wo
Am Freitag, 29. Mai 2015, 10:10:41 schrieben Sie:
> I will now (with some patience) set out to create ignore patterns for my
> local installations of stronswan, and install them on my machines. If they
> may be of any help, when done I can send them to you as a skeleton for
> updated logcheck igno
On 05/17/2013 09:32 PM, Yves-Alexis Perez wrote:
> Seems that the dependency is here from the beginning. Rene, any idea
> if it's really needed?
With the IKEv1 rewrite (strongswan 5.0), it may not longer be needed. I
have not tested it yet.
best regards,.
Rene
signature.asc
Description: OpenPGP
On 2013-05-08 16:17, John Paul Adrian Glaubitz wrote:
> Popcon reports 133 installations, so I wouldn't say "noticeable number"
> of users. Furthermore, the package is available in unstable only and I
> can't seriously imagine anyone running Debian unstable on a server where
> I would havp suspect
On 05/08/2013 03:44 PM, John Paul Adrian Glaubitz wrote:
> On 05/08/2013 03:05 PM, René Mayrhofer wrote:
>> I stopped using havp actively myself. If anybody wants to take over the
>> package (it is simple and works), I'd be happy to give it up.
>
> Well, it has severa
On 05/08/2013 01:55 AM, John Paul Adrian Glaubitz wrote:
> havp seems to have been abandoned both by upstream and the Debian
> maintainer, it should probably be removed from the archives as chances
> are low it will ever meet the quality standards to enter testing.
I stopped using havp actively mys
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-03-14 14:25, Vladimir Stavrinov wrote:
> It may be possible I am only one who encounter this problem,
> because of very unusual configuration:
>
> leftsubnet = 192.168.0.0/24 rightsubnet = 0.0.0.0/0
Could you please send the whole relevant
Hi Harald and Jonathan,
I agree with going for the backports option so as not to delay the
freeze period any more than necessary. However, the typical issue with
openswan will remain in this case: security updates will be more
difficult to backport to the version currently in wheezy (just judg
On 2012-11-24 19:12, Maximiliano Curia wrote:
> The bug seems to be recognized by upstream but there seems to be no work going
> on towards a fix. I've prepared a preliminar patch, but I can't test it right
> now, if you can reproduce it, please test the patch and let me now of the
> results.
>
>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package openswan because it fixes interoperability with
the increasingly important mobile devices (Android and iOS) under
NAT-Traversal conditions.
unblock openswan/1:2.6.38
On 06/25/2012 08:32 AM, Yves-Alexis Perez wrote:
> I didn't want to go that route because I really don't think I'll be able
> to handle this long, but I'm considering doing an NMU of strongswan to
> update it to latest release before freeze.
Unfortunately, I'm still too busy with other projects and
On 2012-04-09 21:58, Adam D. Barratt wrote:
> Policy section 9.3.2:
>
> Files and directories under `/run', including ones referred to via the
> compatibility paths `/var/run' and `/var/lock', are normally stored on
> a temporary filesystem and are normally not persistent across a
> reboot. The `
On 06.04.2012 17:32, Aristov Max wrote:
According to DP "/run is cleared at boot", so some changes should be made to
the upstream code, for example strongswan could keep files directly in /run/lock
directory.
I noticed the problem, when configuration of base-files failed in multistrapped
envir
Hi Jari,
Thanks for doing this! I have nothing against an NMU in this case, so
feel free to push it into the archive, as I will probably need more time
to do the next updates to havp.
best regards,
Rene
On 03/17/2012 04:31 PM, jari.aa...@cante.net wrote:
> Package: havp
> Severity: wishlist
> Ta
Thanks for pointing it out, will be fixed in the next upload!
best regards,
Rene
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 02.07.2011 12:22, Julien Cristau wrote:
Package: openswan
Version: 1:2.6.28+dfsg-5
Severity: serious
Tags: wheezy sid
openswan build-depends on libopensc2-dev, which is no longer built by
the opensc source package.
Why is this supposed to be a serious packaging issue? The
build-dependency on
Package: wnpp
Owner: "Rene Mayrhofer"
Severity: wishlist
*** Please type your report below this line ***
* Package name: dvcs-autosync
Version : 0.3
Upstream Author : Rene Mayrhofer
* URL : http://www.mayrhofer.eu.org/dvcs-autosync
* License : GPL
Programmi
On Wednesday 19 May 2010 23:08:14 Moritz Muehlenhoff wrote:
> havp links against libclamav and is thus affected by #577013. As such
> it needs to be moved to volatile.debian.org and blocked out of stable
> with a RC blocker bug.
From now on, havp will remain in unstable only and updates will be pu
On Tuesday 07 September 2010 01:40:09 Lucas Nussbaum wrote:
> Package: strongswan
> Version: 4.3.2-1.3
> Severity: serious
> Tags: squeeze sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20100906 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in
On Wednesday 18 August 2010 00:57:32 Toni Mueller wrote:
> trying to tackle this bug, I experience a strange problem.
>
> I didn't understand why you included all the Makefiles and the config.*
> files, too, but tried to remove them from the patch and then re-build
> the package.
This seems to be
22 matches
Mail list logo
