Bug#1014411: dvcs-autosync: Should we remove this package?
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 , and it looks like it received no maintainer uploads in the past 12 years. Also, it is affected by python2 removal and missed last Stable release. As a result, I believe it is time to have this package removed from Debian archive. Please let me know if you have any comments on the removal proposal. If there is no objections in the next 14 days, I will proceed and submit a package removal request against Debian FTP Masters. If you have any questions, please feel free to let me know. I agree that, at this point, it should better be removed from the main archive. Moving to Python 3 was blocked because, in that move, I also intended to introduce a better communication mechanism, but ran out of time for this project to do so properly. My development version has never stabilized sufficiently to upload to main. best, Rene
Bug#936459: dvcs-autosync: Python2 removal in sid/bullseye
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 MQTT as a lightweight alternative. However, I haven't found time to actually finish that part, and the current situation isn't helping. Most of the other code should be Python 3 ready and working right now (although I haven't tested in depth), but the sync protocol support isn't there yet. If anybody who is using it has some spare time and want to create a patch to use another XMPP library, I am ok pulling this in. If anybody can invest more time to port over to use MQTT instead, that would be even more welcome :) Am 27.03.20 um 22:32 schrieb Moritz Mühlenhoff: > On Fri, Aug 30, 2019 at 07:16:06AM +, Matthias Klose wrote: >> Package: src:dvcs-autosync >> Version: 0.5+nmu1 >> Severity: normal >> Tags: sid bullseye >> User: debian-pyt...@lists.debian.org >> Usertags: py2removal >> >> Python2 becomes end-of-live upstream, and Debian aims to remove >> Python2 from the distribution, as discussed in >> https://lists.debian.org/debian-python/2019/07/msg00080.html > Hi Rene, > the debian/ directory in your repository on github seems to have > fixed this, can you upload this to archive? > > Cheers, > Moritz
Bug#786133: Bug#639650: dvcs-autosync: diff for NMU version 0.5+nmu1
-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 would lead to a short-term upload at the moment, but have added your diff to my main tree on github already. Thanks, Rene -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJWbs47AAoJEDzCOI+szQadc1sQAKbSmpFp3LqdEw9laXcuAjDd tN1gw8TFxzcCunbAqwXR1/zySRRnbVaJgGkDLP/sDY42bm3ECmhh9tweCcMrlcar +RUkR6BOqaZWy5ndt/2HVdKxrS/2bZeSicMdGOWnmzPybHYjolsfr1I6U5Z/fMWg ZGZUolnIbBfN6mHFyFKAuNIgL0temaxwXgT0HWXvFT8droMWNAQUDvVhcMRvwAQc z2VVjKDoarPzONCpvQ44WBRbQ7/LUc7arSsU0wGnk0zGOLnUCSYwM2ZfWNdBT2V2 FdvHIhm6T37lrmYXSb6C/zmTm6pcAFYYM9kP3eo3ZIEO7mCWBI9IZ52xxWdFXkdi 9AvvoaJldR2rH42CStqajPYA3R2TzrfKWtlZtxVrd1tavmelPoQFTvUBooaZ+oKw JimUvhvJvZ4Zz/8oH85rh8a1018EKrMYOjO60axab9eJrUIwWguZYURi4VwQ+ZSF G2bNOA3A9lTbqbVtHPabkztevC72Q6MFgTkIYE6ug0lB6u/YLmwQB1G/gqrqp/W2 q3WPk4zrBBETXJyq4MY8rj2mqYNffTzv5R7T+1NZOTn6bHv74LJj++j4C9/v6XDu xoRSEJbq3dX7vbSZ1nW0qW40cU8a1WRcah0zHoV773U3iTgKqx8z3ezimmibZcad TKLeUG7PRi46jzjfAQkO =ldSz -END PGP SIGNATURE-
Bug#787156: libstrongswan: configuration file for logcheck ignores completely outdated (useless)
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 ignore files. In the meanwhile, I recommend that you > either remove altogether the current stronswan files in the > /etc/logcheck/ignore.d.* directories, or replace them with empty > placeholders, until you have something more useful to put in them. It will be much appreciated if you can send your patterns - unfortunately, I am currently not using logcheck in production myself (time constraints), and therefore don't notice those issues. best regards, Rene signature.asc Description: This is a digitally signed message part.
Bug#708686: strongswan-ikev2: uninstallable on kfreebsd
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 digital signature
Bug#621379: havp: FTBFS on kfreebsd-*: checking for mandatory locking support... OS not supported
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 to be installed in the first place. The migration blocker bug is there intentionally because of the dependency on libclamav - therefore, havp will only be in volatile, but not in testing. > Again, it has several open RC bugs and shouldn't be used under these > conditions anyway [1]. That is simply not true. The daemon itself works. All RC bugs - while I agree that they should be fixed - are not functionally impairing, but only packaging problems. Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#621379: havp: FTBFS on kfreebsd-*: checking for mandatory locking support... OS not supported
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 several bugs tagged as RC and if neither you or upstream > are longer interested in maintaining havp, I'd rather opt to have the > package removed by the FTP masters. > > Rene, would you agree on removing the package in that case? As far as I know, there is a noticeable number of users, so removing it would be a disservice. Unfortunately, I just don't have time to fix the packaging issues at the moment. The daemon itself worked well enough the last time I used it myself. 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
Bug#621379: havp: FTBFS on kfreebsd-*: checking for mandatory locking support... OS not supported
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 myself. If anybody wants to take over the package (it is simple and works), I'd be happy to give it up. 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
Bug#703032: strongswan: It totally breaks local network
-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 config, because I have not encountered the problem so far. > With this configuration I had a problem in version 4.5 also, but I > have solved it by deleting second default route from table 220. > May be it is bad solution, but it works. Meanwhile with 4.6 > version I've got very different, strange and fatal problem. With > this configuration the machine where this strongswan is running > announces all address of local network 192.168.0.0/24 as it's own, > so all IP address becomes binded with the same MAC address and > network stops working: nobody can connect each other. I'm not sure I fully understand the binding you mention: does the gateway answer all ARP requests when the tunnel is up? Rene -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iQIcBAEBCAAGBQJRRvFgAAoJEDzCOI+szQadDAEP/3QpMHEuCRl8S4WnWkTUGW7H nWGlPpAvUm6EfADHGrxMhnPmMmP5CRPYZOqMAWzPpN1pClKNDkYLNgE6KRkqm0yt wbaJtPQrhHnUfIp4hGOpq7Pq0IITrIJ0qyusAi30hibZ+WO6IC/9L+5zwxVKzMQs 1++EuwHxy3sPDcAnY7E9PYGZjJqXBlP34+8sej7ArNvWlLry6mMMrgjMn7jGlTOx QR8eGX/egCFFwlrx2CJslxcDooNq1lsGx4W+EjLzLm7Sb+nm35DLZ7T5A8xViK/j CwbNDWajk4DPXKLyVdvX7qNEu1pGXIa0mwuOauWUbZHuAqoKav9iPuEmtdLg4+z7 yLZAgDgMvxoD35Em1HI6PUjS4POCFcTf9MJ0LE8wUSrofjU0Lrw//lwOfDQTpBxy BL0TDsdzJxX7/k+g8QhBozEpUYwgpD9MMJjSZgFkVPOjfIKusoWOsMxRLhbOVgIt umadBRRX1021Hfo6+ZWNSiJqXtLHtXkLK/j5QyjrAFbz0bPHol43CUsRIktVmuho Vcl/iOjX5A1eo/oLmqFSJJGceTh700Xae7V6Cp/23Rav1Q4FctoYLg5J2MOSu4eJ CFPo0taG5MFzNBsJhDNm4VHPKb0ZD8uN9sVzp2i/HWxxJKMbgDIxt2lcZkJVNiRf CsHXxd+/ZFycHtcDMtmK =cTIF -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#683683: unblock: openswan/1:2.6.38-1
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 judging from experience). Although I would prefer the new version to enter testing, I understand the caution against such a request. best regards, Rene On 01.01.2013 19:10, Harald Jenny wrote: Hi Harald, Hi Jonathan Harald Jenny wrote: I have retitled the bug request to unblock: openswan/1:2.6.38-1 The version is now in unstable and awaits your (hopefully positive) decision. debdiff attached for reference. diffstat: 598 files changed, 11061 insertions(+), 5908 deletions(-) Is there some subset of these changes that can bring about the same interoperability improvement? Any words to calm fears about the chance of regression among these changes? Well the unblock request was made some months ago at the beginning of the freeze where a new upstream version wouldn't have been such a great issue I presume but now at this stage of the freeze I consider it not appropriate anymore to do such a migration. For the interop fixes maybe they could be backported but openswan upstream is dead and the project already got forked so we won't realy get help and testing for this task. I am not an expert in this area at all, but I fear that without further information the most likely release team reply is negative. I guess so too therefore I'm currently thinking about chancelling the unblock request and instead prepare a backport for wheezy-backports ASAP - Rene what is your opinion on this matter? Hope that helps, Jonathan Yes thanks I will wait for Rene's answer and then presumably close this request, thanks Kind regards Harald -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692129: Preliminar patch, test needed
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. > > I'll try to contact upstream and ask for their input. > > If you want to test this packages you can use the packages published in: > http://maxy.com.ar/debian > > Or you can use the attached patch and apply it to the pptpd package. Thanks for the patch! I would like to get this fixed, but will realistically be unable to test it myself due to "real life constrains"... If anybody can test it in a different setting to verify that it fixes the bugs and doesn't break other cases, I am happy to do an 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
Bug#683683: unblock: openswan/1:2.6.38-1~experimental+1
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-1~experimental+1 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664190: strongswan NMU
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 won't realistically managed to do much in the next 3-4 weeks. Therefore, please feel free to NMU until my next upload (which will be after that time). > Right now, I have no real idea what is your method to package new stuff > in strongswan, so it'd be really nice if you could give me some pointer > so I can do the work directly in your repository. I use git-buildpackage, and the repo is on Alioth. There's really not much process besides the standard git-Debian-packaging update scripts, manual compiles, manual checks, changelog updating, and uploading. 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
Bug#667764: strongswan-starter: package must not include /var/lock/subsys
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 `init.d' scripts must handle this correctly. This will > typically mean creating any required subdirectories dynamically when > the `init.d' script is run. I stand corrected and am happy to include a change for the init script to create the /var/lock directory and remove the directory from the binary package. Unfortunately, I am not completely swamped with real-world projects and will probably be unable to make even this simple change within the next few weeks. NMUs for this issue are welcome, as are co-maintainers for strongswan. 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
Bug#667764: strongswan-starter: package must not include /var/lock/subsys
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 environment: its postinst script assumes /var/lock to be empty. The subdirectory under /var/lock is used to restrict its permissions for more secure locking, and upstream will most probably not change it. I do not currently agree that this is in violation to Debian Policy, so unless you can convince me that a change will indeed improve the package, I will mark this as wontfix and lower the priority to normal. 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
Bug#664346: [PATCH] havp: Helping to update to packaging format 3.0
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 > Tags: patch > > Hi, > > The dpatch patch management system has been deprecated for some time. The > Lintian currently flags use of dpatch packages as an error. The new 3.0 > packaging format is an improved version which, among other things, contains > patch management built-in. For more information, see: > > http://wiki.debian.org/Projects/DebSrc3.0 > > I had some free time; see attached patch to migrate to new package > format. Note that all files in debian/patches/* are canocalized to > *.patch. > > Let me know if there is anything that needs adjusting or if it is ok > to upload this version in a NMU in case you are working on other > issues needing attention. > > Thanks, > Jari > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637387: dvcs-autosync: specified Vcs-git is not public accessible
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
Bug#632449: openswan: obsolete build-dependency: libopensc2-dev
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 libopensc2-dev eases backporting to lenny, which still a few people (me included) do. Rene -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#620962: ITP: dvcs-autosync -- dvcs-autosync uses inotify and XMPP messages for nearly-instanteneous commit/push/pull handling of DVCS systems (tested mainly with git) for a distributed Dropbox/etc
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 Programming Lang: Python Description : dvcs-autosync uses inotify and XMPP messages for nearly-instanteneous commit/push/pull handling of DVCS systems (tested mainly with git) for a distributed Dropbox/etc. replacement For details, please see http://www.mayrhofer.eu.org/dvcs-autosync signature.asc Description: This is a digitally signed message part.
Bug#582306: Links against libclamav
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 pushed to stable-volatile. This release blocker bug will remain open to prevent a transition to testing. best regards, Rene signature.asc Description: This is a digitally signed message part.
Bug#595885: strongswan: FTBFS in squeeze: No package 'libnm_glib_vpn' found
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 a squeeze chroot, your package failed > to build on amd64. Could you please try to rebuild with the current 4.4.1-3 package which was unblocked to transition from sid to squeeze? The libnm_glib_vpn package is no longer a dependency. best regards, Rene signature.asc Description: This is a digitally signed message part.
Bug#593313: building strongswan
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 a bad interaction between quilt dpkg-source format and svn- buildpackage. I will be trying to build strongswan in pbuilder here on my machine. best regards, Rene signature.asc Description: This is a digitally signed message part.
