Bug#919587: bringing back Imapsync
Hey, I'm not working on imapsync right now. To be honest, I'm using mbsync myself right now and completely satisfied with it. Feel free to package imapsync and push it to Debian, I'm as an old maintainer not interested in this right now, because I don't have the free time. Sorry about this and wish you the best of luck! Cheers, Gergely On 2019-01-22 14:56 (Tuesday), Markus Raps writes: > Dear RISKO Gergely, > > as in > https://www.debian.org/doc/manuals/developers-reference/ch05.html#reintroducing-pkgs > described > i ask you, are you working on a comeback for imapsync in debian? > Can I help you in any way? packaging, building, testing ?
Bug#891036: libusbip: error: port number exceeds 128
Dear Ben,
The issue is definitely not fixed by this in 4.14.17-1:
* usbip: Reduce USBIP_VHCI_HC_PORTS to 15, the maximum allowed for SuperSpeed
hubs (Closes: #878866)
On the other hand simply increasing the limit in the userspace library
from 128 to 256 fixes the issue on my computer running
linux-image-4.16.0-1-amd64 (4.16.5-1). Please note that the patch is
only a userspace change in the usbip package, not a kernel change.
I tested the change without even rebuilding the package, just building
the userspace usbip executable with autogen+configure+make in the
tools/usb/usbip subdirectory and I managed to pass through a usb
device. No oopses, no problems, device is working as expected.
Cheers,
Gergely
--- linux-4.16.5.orig/tools/usb/usbip/libsrc/vhci_driver.h
+++ linux-4.16.5/tools/usb/usbip/libsrc/vhci_driver.h
@@ -13,7 +13,7 @@
#define USBIP_VHCI_BUS_TYPE "platform"
#define USBIP_VHCI_DEVICE_NAME "vhci_hcd.0"
-#define MAXNPORT 128
+#define MAXNPORT 256
enum hub_speed {
HUB_SPEED_HIGH = 0,
Bug#857130: os-prober: add support for veracrypt system encryption on UEFI
Package: os-prober Version: 1.74 Tags: patch Veracrypt system encryption for Windows 7/8/10 on UEFI is working by creating an additional efi program on the EFI partition. If this efi program is added to the GRUB menu, then I can successfully boot my system encrypted Windows system from GRUB. Since in Debian, GRUB uses os-prober to get the additional menu items to present for additional OSes, adding the attached file to /usr/lib/os-probes/mounted/efi/15veracrypt results in a correctly working Veracrypt GRUB menu item. Tested on Windows 10 Home, have no idea about other editions or versions, but most probably this will work for them. Note, that this is only for UEFI, I have no idea how to add Veracrypt to the GRUB menu on MBR systems. Note, that most of this is a copy-paste and customization of the 20microsoft script. 15veracrypt Description: Binary data
Bug#762910: lines longer than 39 characters are mishandled in /proc/acpi/wakeup
Package: acpitool
Version: 0.5.1-3
Tags: patch
While parsing /proc/acpi/wakeup, src/acpitool.cpp assumes that lines are
maximum 39 char long (40 including the terminating NUL character at the
end of C strings).
Since I have a line in /proc/acpi/wakeup that is exactly 40 char long,
the tool doesn't work (it hangs up when it hits that line, consuming
100% CPU forever).
The attached patch changes this behavior to assume maximum 79 char long
lines by increasing the buffer size to 80.
diff -ur acpitool-0.5.1/debian/patches/wakeup.patch acpitool-0.5.1.patched/debian/patches/wakeup.patch
--- acpitool-0.5.1/debian/patches/wakeup.patch 2014-09-26 10:20:52.0 +0200
+++ acpitool-0.5.1.patched/debian/patches/wakeup.patch 2014-09-26 10:16:07.163701983 +0200
@@ -13,15 +13,44 @@
have a device called "LID" which is 3 characters long.
Instead of using a fixed size for the device we split the line
on the first tab (\t) and use the first part.
+
+ * The length of lines in /proc/acpi/wakeup can have more than 39
+ characters, I have one with exactly 40. So let's increase the
+ reading buffer to 80 characters.
---
src/acpitool.cpp | 23 +++
1 files changed, 11 insertions(+), 12 deletions(-)
-diff --git a/src/acpitool.cpp b/src/acpitool.cpp
-index 2a610a5..71e01d7 100644
a/src/acpitool.cpp
-+++ b/src/acpitool.cpp
-@@ -460,16 +460,14 @@ int Show_WakeUp_Devices(int verbose)
+Index: acpitool-0.5.1/src/acpitool.cpp
+===
+--- acpitool-0.5.1.orig/src/acpitool.cpp
acpitool-0.5.1/src/acpitool.cpp
+@@ -416,7 +416,7 @@ int Do_Fan_Info(int verbose)
+ int Show_WakeUp_Devices(int verbose)
+ {
+ ifstream file_in;
+-char *filename, str[40];
++char *filename, str[80];
+
+ filename = "/proc/acpi/wakeup";
+
+@@ -437,13 +437,13 @@ int Show_WakeUp_Devices(int verbose)
+ }
+ else
+ {
+- file_in.getline(str, 40); // first line are just headers //
++ file_in.getline(str, 80); // first line are just headers //
+ cout<<" "<
Bug#569786: vlogger: [PATCH] Add option to write out access.logs without chopping the vhost off the beginning
tags 569786 wontfix
stop
Dear v.nix.is,
I marked this request as wontfix, because implementing this seems to be
a duplicate effort, since you could just put
LogFormat "%v %v %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\""
combined
into your apache config. That way you can put the second %v wherever
you want on the line and it will be written out.
So your use-case can be achieved with a bit of a configuration change,
therefore I don't see it appropriate to add yet another option.
The only issue I forsee, is that vlogger unfortunately uses other
data column numbers directly like this:
my $reqsize = $this_line[10];
or:
$reqsize = $this_line[1] + $this_line[2];
If someone would submit a patch that adds parameters to specify the
reqsize column and/or mod_logio columns, that would be OK with me.
But I don't know how many people are using the mysql statistics feature
anyways... Seems to be a big hack, to be honest.
If you don't agree with this wontfix, please reply to the bugreport and
point out your reasons.
Thank you for taking the time to report this,
Gergely
On Sun, 14 Feb 2010 09:59:48 +, "v.nix.is" writes:
> Package: vlogger
> Version: 1.3-3
> Severity: wishlist
>
> I found that using vlogger with programs such as awstats that expect
> logs to be in an unaltered combined log format doesn't work. awstats
> for example will simply die on any line that doesn't include a host.
>
> So I made a small change to vlogger to add a -p option for
> "PassThrough mode". It's a very small patch and with it vlogger won't
> munge log lines at all before writing them to subdirectories as it
> does normally.
>
> The patch is here:
> http://github.com/avar/linode-etc/commit/94f0d7d22773d4430f1490ddea9858f2cbcd50e8
>
> I didn't modify the man page or other things in the package because
> this works for me and I wanted to see what the author thought of it.
>
> -- System Information:
> Debian Release: squeeze/sid
> APT prefers testing
> APT policy: (650, 'testing'), (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 2.6.32-x86_64-linode11 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages vlogger depends on:
> ii libtimedate-perl 1.2000-1 collection of modules to
> manipulat
> ii perl 5.10.1-9 Larry Wall's Practical
> Extraction
>
> vlogger recommends no packages.
>
> Versions of packages vlogger suggests:
> ii libdbi-perl 1.609-1Perl Database Interface (DBI)
>
> -- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#407047: -n option is documented, handled but not parsed
Hi, I've uploaded the fix to this issue. I also added the following collab-maint repository: http://anonscm.debian.org/gitweb/?p=collab-maint/vlogger.git;a=summary If you use vlogger this heavily, I urge you to create a vlogger fork on github or somewhere and make your fixes there. That way I won't be in the hotspot for reviewing and adding patches. Once you reached a version that you think should be released into debian, tag it as 1.4 (or something) and open a bug report on vlogger asking me to upgrade to that version. It's a lot easier to collaborate in git and apply patches quickly in a github repo than sending upstream patches to the BTS. This is also the only way to have these fixes move to Fedora, BSDs, etc. Sorry, but I currently can't volunteer to maintain vlogger and to continuously review major new patches and features. Either outside or inside Debian. Thanks, Gergely On Thu, 16 Jan 2014 12:10:20 +0100, Declercq Laurent writes: > Hello ; > > First, sorry for my previous report.. It was too much sarcastic for > you as I see. > > Well, I can provide you a patch for all the bugs linked here. It's not > a problem for me since we are using our own vlogger version for our > control panel. Therefor, I would be happy to help as long you accept > those patches. > > I can also add some improvements. For the record, when using the DBI > tracker feature, Apache will fail miserably if the MySQL connnection > is failing for any reason. Well, in our version I've revisited that > part to make vlogger more safe. Eg, if the MySQL connection fail for > any reason, vlogger will simply turn off that feature and continue its > main job. Of course, an option should be added to let the admin decide > whether or not the script should follow such a behavior. > > Another thing is about how vlogger is reading traffic data from > mod_logio. A sample line should be added to warn the admin that the > logio variables should be added just after the %v variable. Or even > better, vlogger should simply search for those variables in the whole > logFormat string instead of just make assumption on their position... > > As you can see, I'm ready to help you because I support Debian like > you cannot ever imagine. The fact is that I suprised to see such bug > reported since a while, which is not fixed yet. Even if the upstream > author doesn't works much for a new release, it's not our problem. As > long the vlogger is part of the Debian repository, it should be > fixed. I know that you prefer warn the upstream author about such a > bug and wait for a new release but this do not work as you can see. > > Thank you. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#407047: -n option is documented, handled but not parsed
On Mon, 13 Jan 2014 19:26:36 +0100, Laurent Declercq writes: > Package: vlogger > Version: 1.3-3.1 > Followup-For: Bug #407047 > > Dear Maintainer, > > This bug affect all vlogger version in Debian and Ubuntu. > > It's so simple to fix this bug that I'm wondering what the > maintainer of this package is doing... I'm doing well, thanks for asking. Apart from reading these kind of hatemail comments in Debian bug reports... :) In this package there are two other bugs since 1.3 which never went upstream: - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=302176, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645623. There are no new upstream releases since 1.3 to fix these issues, so even if we continue patching this in Debian, folks will have to duplicate the work in all other systems, like Fedora or BSDs. If you really want to help instead of just sending around opinionated rude emails to folks who work on stuff in their free time, you should take ownership of upstream maintenance of the code. Maybe you should email the guy who already started this 4 years ago: https://github.com/halfdan/vlogger (google search for "vlogger github"). Or you can just fork 1.3 and add these three bugfixes, call it 1.3.1 (or 1.4) and then ask the distributions to use your source code version. This is not to say that I'll not fix this by patching it in Debian. I'd just like to ask you that in the future you either: - ask _nicely_, - and/or be constructive and do your part of work where you can. There is also some debugging task to do: - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506246 Just have to replicate the environment on a machine and try it out with a lot of requests to see if we can reproduce at least. Or some little, easy issues: - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299796, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299872, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=299873, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569786, - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735195. Thank you. Cheers, Gergely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#695722: shaperd: cobwebby package description
Hi Justin, Sorry for getting back to you so late. Yes, this package is doomed, I've just requested removal: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708220 Once it's through, I'll close this bug too. Thank you for your help and for noticing me about the kernel change! Gergely On Tue, 11 Dec 2012 22:46:15 +, Justin B Rye writes: > Package: shaperd > Version: 0.2.1-5.2 > Severity: wishlist > Tags: patch > > The package description for shaperd clearly hasn't been updated for > about a decade, and needs some attention. > > # Description: A user-mode traffic shaper for tcp-ip networks > > DevRef-noncompliant initial capitalised indefinite article. > > The protocol name is also mis-capitalised, but this reference to > "TCP/IP networks" seems misplaced anyway: the point isn't that this is > a traffic shaper for the Internet (as opposed to NetBIOS), it's that > it's a TCP/IP traffic shaper. > > # Shaperd is a user-mode program that can shape traffic passing through > # a Linux box. As it runs as a normal daemon, some kind of packet-forwarding > > We don't need to belabour the fact that the daemon runs in userspace > quite so heavily. Are there any Debian packages that contain > kernelspace daemons? > > # mechanism is needed. This can be done with the BSD divert sockets patch > # for Linux 2.2, or with netfilter's built-in libipq under Linux 2.4. > > This is the part that caught my eye. Debian hasn't officially > supported anything as ancient as Linux 2.4 (let alone 2.2!) for > several stable releases. Meanwhile, libipq has been deprecated for > almost as long and won't work with anything newer than 3.4. So I > suspect this package is probably doomed, but meanwhile here's a > suggested patch for the package description: > > | Description: user-mode TCP/IP traffic shaper > | Shaperd is a user-mode daemon that can shape network traffic passing > | through a Linux box. It depends on netfilter's ip_queue module for packet > | forwarding. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#708220: ftp.debian.org: RM: shaperd -- RoM; not compatible with new kernels, not maintained by upstream
Package: ftp.debian.org Severity: normal Hi, Please remove shaperd from unstable. There has been no new release since 2002: http://freecode.com/projects/shaperd And now it's not usable anymore with newer kernels, since IPQ is gone: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707444 Also, the whole traffic shaping infrastructure in the kernel got a lot more mature and it's well documented now; so easy to configure but hacky solutions, like shaperd is not so needed as in 2002. Thank you, Gergely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#692914: FTBFS against libav9 in experimental
On Sat, 10 Nov 2012 14:08:24 -0500, Tiago Bortoletto Vaz writes: >> I'm not sure if you have been asked before, but what do you think about >> maintaining ffmpeg2theora under the pkg-multimedia-maintainers umbrella? > > This makes sense. I'll move it to pkg-multimedia-maintainers. > > RISKO Gergely, do you mind? I'll keep you as uploader. Also, please ping me if > you want to be added to pkg-multimedia-maintainers in alioth. Yes, I agree, this makes a lot of sense. Please add me to the alioth group and I will try to spend some time on this work if I can. But this transition will make things easier if I can't, which is unfortunately more probable :( Thank you for doing this! Gergely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#675262: Freecell Solver's Package In Debian Sid is Out-of-Date
Hi, Sorry for being late on this and thanks for the notice. If there is another new release in sight soon, then yes, I appreciate if you do that before we do the new debian release. Gergely On Wed, 30 May 2012 22:21:57 +0300, Shlomi Fish writes: > Package: freecell-solver > Version: 3.4.0-1 > > The Freecell Solver package in Debian unstable is out-of-date - it's at 3.4.0 > and there's already 3.10.0 , see: > > http://fc-solve.shlomifish.org/download.html > > Please update it. > > I am the maintainer of Freecell Solver, and I could also publish a new 3.12.0 > release (with some improvements), based on the current fc-solve master branch, > just to prevent the extra packaging work. Please let me know if you would be > interested. > > Regards, > > -- Shlomi Fish -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#647676: thrust: [patch] implement SDL backend support
Hi Martin, Thanks a lot for caring about this. You are right, svgalib is kind of the past. I'm gladly willing to accept this patch. Unfortunately I don't have a lot of time, so please also try to update the manpage and stuff, I will of course do some testing myself and upload the new package. Thanks a lot once more! Gergely On Sat, 05 Nov 2011 01:26:27 +, Martin Hradil writes: > Package: thrust > Version: 0.89c-3.5 > Severity: wishlist > > Greetings, > > current Thrust is currently hard to run because SVGAlib doesn't run > everywhere and some people don't have X set to 8bits per color. > So, I've implemented a SDL backend which I'm attaching here. > > It's complete in the sense you can use it to play thrust in a 320x200 SDL > window using the default controls and everything works. > It's currently missing key settings (the default controls are hardcoded) and > any kind of zoom (which might be useful). > > It simply adds two more files (src/SDL.c and src/SDLkey.c). The included > patch also adds lines which were necessary to add to Makefile, but it adds > them to the beginning so you might have to move them around a bit. Sorry, I > really know nothing about autoconf and stuff. > > I'm sending these patches to you, the Debian maintainer for thrust, because > the last upstream is 5 years old so presumably dead. > If you're willing to accept them I'll finish the missing things. Feel free to > provide any suggestions. > > Regards, > Martin Hradil > > -- System Information: > Debian Release: wheezy/sid > APT prefers oldstable > APT policy: (500, 'oldstable'), (500, 'testing'), (500, 'stable'), (400, > 'unstable'), (101, 'experimental') > Architecture: i386 (i686) > > Kernel: Linux 2.6.39-2-686-pae (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages thrust depends on: > ii libc6 2.13-21 > ii libice6 2:1.0.7-2 > ii libsm62:1.2.0-2 > ii libsvga1 1:1.4.3-31 > ii libx11-6 2:1.4.4-2 > ii libxext6 2:1.3.0-3 > > thrust recommends no packages. > > thrust suggests no packages. > > -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#609845: ftp.debian.org: RM: imapsync -- RoM; author doesn't want us to distribute his program
On Wed, 26 Jan 2011 15:57:40 +0100, Gilles LAMIRAL writes: >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609845#60 >> >> Please observe, the short "No." it contains everything. > > It contains too much. I repeat with precision "No. Do what you want". > I promise I won't complain anymore about the fact imapsync is on Debian or > not. Okay, then this was a bit of a misunderstanding, but my decision is still final. Sorry about the confusion. If anyone wants to continue whatever way they see fit, the git repo, containing the packaging can still be found at http://git.debian.org/?p=collab-maint/imapsync.git;a=summary and I will not remove it. Happy hacking, Gergely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#609845: ftp.debian.org: RM: imapsync -- RoM; author doesn't want us to distribute his program
Dear Jeff, Thank you for your opinion. Please consider the fact that the author explicitly asked us to _NOT_ distribute his software. I do not believe that Debian is (or should be) an organization that disregards a request like this. The author explicitly said that he is trying a new business model and it is clear that our distribution makes that harder. If you do not agree with this reasoning and you want to go the opposite way, feel free to buy the source from Gilles (or download an old version for free if you are really that cheap), relicense it as GPL, find a new name, find a new maintainer in Debian and upload a new package. But I do not want to be part of it and I sincerely hope that other Debian Developers feel the same way and honor Gilles work enough to not intentionally try to kill his business. > I do not understand why you wish to remove from the debian archive > software that debian users may rely on (as far as I can see from the > original report, not everyone's use of the version Debian ships hits the > reported problem), just because of a possible license problem in a > *different version* of the software than debian ships. So please accept my explanation and please understand, that I do not abandon the package because of the license problems, but because of the request of the upstream author. > As far as I can see, the author of this software has even said in a > message in this bug report that "You can even make [this software] a GPL > software"[1], which I understand him to mean that the intent of the new > license is to be GPL-compatible! You are reading very selectively. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609845#60 Please observe, the short "No." it contains everything. Gilles: if I misunderstood you, please say it, but currently I do not see any reason why Debian should distribute this software against your will. Jeff: the package is already removed, so our argument is quite hypothetical anyway, a new upload has to be done if you want to see the package again in unstable. Happy hacking if you are willing to work on that, with the current status of the upstream I am not willing. Thanks for your mail, Gergely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#609845: ftp.debian.org: RM: imapsync -- RoM; author doesn't want us to distribute his program
Package: ftp.debian.org Severity: normal Hi, Please remove imapsync from unstable. New versions of the program can only be downloaded for money from the upstream author's website and therefore distributing the program for free in Debian is not requested by him anymore. The whole discussion can be found in #609845. Thank you, Gergely On Sun, 23 Jan 2011 23:33:02 +0100, Gilles LAMIRAL writes: > Hello, > >>- do you want Debian to continue distributing your program >> (http://packages.debian.org/unstable/mail/imapsync)? > > No. > > I thank you very much for all the time and skill you spent packaging imapsync > in Debian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#609845: situation of imapsync and Debian (was: Re: Bug#609845: huge memory leak when syncing large mailboxes)
Hi guys, Executive summary for new recipients (debian-legal): imapsync has changed its distribution policy, downloads from the author's original website are not free (as in beer) anymore. Of course `apt-get source' or `apt-get install' is still free, as the package is still in the Debian archive. The licensing hasn't changed, Debian's distribution of the package is still legal. As the maintainer of the package, I am starting discussion about the future of this package in the archive. Details: Sorry for hijacking this thread for license/distribution discussions, but I guess this is the best way to keep the people notified who are already in this discussion. On Fri, 14 Jan 2011 06:09:22 +0100, Gilles LAMIRAL writes: > So I have no shame about imapsync and won't ever have any. No shame on either sides. I totally agree: you should have a safe and nice living and you should have enough money to pay for it. On an orthogonal note, I am not feeling comfortable about dealing with imapsync Debian packaging anymore. It is my (sparse) free time and I would like to commit it to projects that are free (as in speech _AND_ beer) and easily downloadable from the original author without any kind of payment and/or license reading/investigation. Please accept my decision about this. Thanks for all the time in the past you have spent on discussing with me, dealing with Debian stuff. I do not have the legal skills to discuss wether your webpage and your distribution policy of imapsync (http://www.linux-france.org/prj/imapsync/) is compatible or not with the debian social contract. I will leave this to the debian-legal people. Now imapsync doesn't have a debian maintainer anymore, so we will have to look for a new one. You can read about the Debian process for this at http://www.debian.org/devel/wnpp/. Of course the upstream author's opinion is very important to us, so Gilles, let me ask you a few questions: - do you want Debian to continue distributing your program (http://packages.debian.org/unstable/mail/imapsync)? - if yes, do you want us to update the package for later versions? - if yes, will you provide the source code to us for free and allow us to redistribute it? If it is needed, I am happy to contact the ftp masters to make any necessary deletion from the Debian archive as quickly as possible. Thanks again for working with us and I wish you good luck with your business around imapsync and/or other projects. Gergely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#589387: Please deal with this bug.
Hi, On Wed, 5 Jan 2011 09:49:32 +0200, Shlomi Fish writes: > On Tuesday 04 Jan 2011 13:59:43 Gergely Risko wrote: >> Hi Shlomi, >> >> Sorry for the delay, I will try to do this update over this week. >> > > OK, thanks for the heads-up. But isn't Squeeze frozen? According to: http://lists.debian.org/debian-devel-announce/2010/12/msg2.html Squeeze is frozen, you are right in that. I can do the upload nevertheless: it will update in unstable and migrate to the next testing release (wheezy), when it will be opened. I know this is late compared to being accepted to squeeze, but I can't really do anything about this. Gergely -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#589387: Please deal with this bug.
Hi Shlomi, Sorry for the delay, I will try to do this update over this week. Happy new year, Gergely On Sun, 26 Dec 2010 13:18:59 +0200, Shlomi Fish writes: > Can this bug be dealt with already? I've lost patience. > > Regards, > > -- Shlomi Fish -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
