Bug#666851: Apache 2.4 upload date scheduled for May 30
Hi, To minimize the breakage to our Sid users, we'd ask all of you having a transitioned package ready in Experimental, to make an upload to Sid AFTER the 13:52 UTC dinstall, and BEFORE 19:52 UTC [1]. Apache 2.4 is in Unstable now. Please upload asap, or let me know if I shall NMU. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#666851: Apache 2.4 upload date scheduled for May 30
Hi Tony, On 30.05.2013 22:30, tony mancill wrote: I'll take a look at updating the package tonight based on Damien's work on libapache-mod-jk 1:1.2.35-1. Or if you have a debdiff ready to go, please attach it to the bug report. No need for an NMU. no I don't, but I had the same plan as you, that is to take the existing package in Experimental and possibly upload that to Sid. Thanks for your work. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#666851: Apache 2.4 upload date scheduled for May 30
Hi, On 30.05.2013 23:53, tony mancill wrote: you to work on this if that's okay with Arno, timing-wise. My Debian dance card is full... :) I'm perfectly fine if you go ahead that way. It's your package after all, so it's not exactly me to decide who is best suited to upload your own packages. :) I don't think one day makes much of difference in look of all the havoc caused by my upload earlier for modules which have no fix at all. Thanks for working on it so early! I just wanted to make sure your module gets fixed in a timely manner because it is one of the more important ones, where many people may be using it. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#666851: Apache 2.4 upload date scheduled for May 30
Hello fellow maintainers, we are ready to upload Apache2 2.4 to Debian Sid now. This means the transition is effectively starting now, and going to break your modules. We have scheduled the upload for May 30, 2013 BEFORE the 19:52 UTC dinstall on ftp-master. To minimize the breakage to our Sid users, we'd ask all of you having a transitioned package ready in Experimental, to make an upload to Sid AFTER the 13:52 UTC dinstall, and BEFORE 19:52 UTC [1]. Let us know if you need a sponsor, or our help to upload your packages in that time window. Please note, you could also use the DELAYED queue to make timed upload [2]. [1] http://ftp-master.debian.org/#dinstall [2] http://ftp-master.debian.org/deferred.html -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#666851: Apache 2.4 transition is ready in VCS
Hi, duly noted! Thanks for you work. I'll come back to you once other modules from #707024 are ready to be uploaded, so that we can do coordinated rush to unstable. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Reboot Apache2 2.4 transition
Hi there, Now that Wheezy is ehrm virtually released ..., we'd like to reboot the Apache 2.4 transition process as soon as possible. In other words, we'd like to break Sid - as far as Apache is involved - in a foreseeable future. With your permission to proceed as suggested pending, we'd like to propose this procedure to continue with the Apache 2.4 transition: *) Aim for an upload of Apache 2.4 in June. The exact date is not fixed and determined by two factors: You approving the process itself, and the availability of a 2.4 port for certain reverse dependencies (see next point). *) Since this upload is going to break all existing module reverse dependencies, this causes bad breakage to users of Apache in Sid. We're aware of that, but it can't be avoided entirely since a transition in Experimental only does not seem to work out that well, as we're trying to prod the maintainers of affected packages for over a year. However, to smoothen the transition as much as possible, we'd like to wait with an upload to Sid until these reverse dependencies have updated packages available and then do a coordinated upload with the respective maintainers (they're all CC:-ed): - mod_php - mod_security - mod_wsgi - mod_dnssd (gnome-user-share) - mod_jk - mod_fcgid - subversion This is a somewhat biased choice, based on the popularity of the modules, and their relative importance in the Apache eco-system itself. PHP, and WSGI for example have reverse dependencies on their own, which are affected by our transition, too. Please maintainers of these package, do help us so that we can do the upload in a timely manner. Maintainers, if you need help us to transition with these modules, let the Apache maintainers know. We'll help you. *) Once the package is uploaded to Unstable together with a reasonably small subset of reverse dependencies as defined above, we'd like to successively increase the amount of transitioned packages to a larger amount (see the full list in previous posts) before considering a migration to Testing. It is up to decide together with you when exactly this is going to happen, but I do not suspect this being the case until (end of) summer. At some point we'd like to ask you to remove remaining non-transitioned packages from Testing so that we migrate the already transitioned packages, including our own. Until then, we'd file a testing migration blocking bug against our own package, so that it can't migrate to Testing by accident. *) Once the package has reached Testing, we'd like to address a transition of web-applications reverse depending on Apache. This cannot be parallelized easily, because most of them are depending on some other third party module, too. On the upside, web applications are somewhat broken during the migration, but this may only affect the integration of the Apache web server, whereas the application itself remains functional. Does this make sense to you? -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#666851: Apache2.4 transition: reboot
Dear maintainers, now that the work is done and Debian 7.0 (Wheezy) is released [*], we are booting the Apache 2.4 transition process again. If you did not already, please subscribe to transition bug #661958 to keep up with our transition plan in detail as this IS going to affect your package. Unless the Release Team is going to assign us another slot to start the transition we are going to upload Apache 2.4 to Debian Sid at some point in June. If you do not prepare a package which works together with the Apache 2.4 server ABI by then, it is going to stop working at that time. Let me emphasize again you do need to make adjustments in the source of your package to get it working with Apache 2.4. Moreover, the APIs slightly changed from 2.2 to 2.4 so that some modules may require some porting. On the upside, it has been over a year that Apache 2.4 was released and many upstreams made compatible releases. Moreover, porting is easy in most cases and I've filed patches to some of your modules. Either way, if you are trying to load existing module from Sid into an Apache 2.4 web server is going to fail at runtime which renders your package virtually useless. We are planning to make the transition as smooth as possible to our users. Thus, we do not want to let the Apache 2.4 package migrate to Testing anytime soon. Instead, we'd like to let it migrate together with a bunch of transitioned third party modules (i.e. your packages). Please help us to make this happen soon. While we invite everyone to provide updated packages as soon as possible, don't hesitate to contact us if you feel like, we should wait for you and your package when considering a migration to Debian Testing. All packages which are not yet transitioned at that point will eventually be removed from Testing. Please prepare updates for your packages NOW and upload an upgraded package to Debian Experimental and/or have a patch ready in your VCS. In the case of the latter, please tag this bug pending. We chose some very important external modules to be a blocker for our upload to Unstable. That is, we will wait for you until we are uploading to Unstable, so that we can do a coordinated upload to mitigate the impact of Sid users. If you are the maintainer of such a blocker module, we'll contact you separately again. If you feel like you should be on the blocker list denoted in #661958 please let us know as soon as possible. [*] yah, it's not yet formally speaking -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
