Re: Future requirements for specifying supported Python versionsand transition support
* Scott Kitterman (deb...@kitterman.com) [100626 23:51]: There is a bit of difference over how to specify which versions to build for, but if we don't need to expose it externally (and I don't see a case for this), then it's an internal matter for package build systems as long as they support a requirement that arch: any packages be binNMUable for new Python versions. There are pre-ideas that we might be able to binNMU arch=all-packages as well - nothing that will come too early, but it might be useful to not depend on the fact that we only binNMU arch=any. We've discussed this pretty broadly on debian-pyt...@l.d.o and in #debian- python, so I think we have enough buy-in. In spite of some discussion I have seen, I haven't followed that enough to have an own opinion. Anyways, I trust you that you do it right - I was just stating what are the requirements of the release team (and why), and I think they're sensible (and if not, please feel free to say so). Andi -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100627092844.gj13...@mails.so.argh.org
Re: Future requirements for specifying supported Python versionsand transition support
Andreas Barth a...@not.so.argh.org wrote: * Scott Kitterman (deb...@kitterman.com) [100626 23:51]: There is a bit of difference over how to specify which versions to build for, but if we don't need to expose it externally (and I don't see a case for this), then it's an internal matter for package build systems as long as they support a requirement that arch: any packages be binNMUable for new Python versions. There are pre-ideas that we might be able to binNMU arch=all-packages as well - nothing that will come too early, but it might be useful to not depend on the fact that we only binNMU arch=any. No. We don't plan to depend on this. Arch all binNMU would be quite welcome and would help us solve some other issues around making Python transitions easier and more robust. Scott K -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2dfaf7b6-03af-43f5-99ae-97046fa45...@email.android.com
simplesamlphp not migrating to testing
Hi, My package simplesamlphp is not migrating to testing: Excuse for simplesamlphp * 23 days old (needed 10 days) * simplesamlphp/i386 unsatisfiable Depends: php5-mhash (= 5.2.0) * Valid candidate In squeeze php5-mhash is provided by php5, in Lenny this is a separate package. I want to Depend on php5-mhash to also keep the dependencies correct in a Lenny context. What can I do to have the package migrate? Thanks, Thijs signature.asc Description: This is a digitally signed message part.
Re: simplesamlphp not migrating to testing
On Sun, Jun 27, 2010 at 17:04:27 +0200, Thijs Kinkhorst wrote: Hi, My package simplesamlphp is not migrating to testing: Excuse for simplesamlphp * 23 days old (needed 10 days) * simplesamlphp/i386 unsatisfiable Depends: php5-mhash (= 5.2.0) * Valid candidate In squeeze php5-mhash is provided by php5, in Lenny this is a separate package. I want to Depend on php5-mhash to also keep the dependencies correct in a Lenny context. What can I do to have the package migrate? Change the Depends to php5 (= $whatever) | php5-mhash? Cheers, Julien signature.asc Description: Digital signature
Bug#587341: transition: react / lwt / ocsigen
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Hello, The following packages need to go to testing together: easy react/0.9.2-1 lwt/2.1.1-1 ocsigen/1.3.3-1 nurpawiki/amd64/1.2.3-4 nurpawiki/armel/1.2.3-4 nurpawiki/hppa/1.2.3-4 nurpawiki/i386/1.2.3-4 nurpawiki/ia64/1.2.3-4 nurpawiki/kfreebsd-amd64/1.2.3-4 nurpawiki/kfreebsd-i386/1.2.3-4 nurpawiki/mips/1.2.3-4 nurpawiki/mipsel/1.2.3-4 nurpawiki/powerpc/1.2.3-4 nurpawiki/s390/1.2.3-4 nurpawiki/sparc/1.2.3-4 Thanks in advance, -- Stéphane -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100627170402.13575.1550.report...@korell.up7.fr
Re: simplesamlphp not migrating to testing
On snein 27 Juny 2010, Julien Cristau wrote: My package simplesamlphp is not migrating to testing: Excuse for simplesamlphp * 23 days old (needed 10 days) * simplesamlphp/i386 unsatisfiable Depends: php5-mhash (= 5.2.0) * Valid candidate In squeeze php5-mhash is provided by php5, in Lenny this is a separate package. I want to Depend on php5-mhash to also keep the dependencies correct in a Lenny context. What can I do to have the package migrate? Change the Depends to php5 (= $whatever) | php5-mhash? OK, I will do that but I'm just checking to avoid trial-and-error, as it was a surprise to me in the first place that testing migration doesn't consider Provides. Thanks, Thijs signature.asc Description: This is a digitally signed message part.
Re: simplesamlphp not migrating to testing
On Sun, Jun 27, 2010 at 19:36:55 +0200, Thijs Kinkhorst wrote: OK, I will do that but I'm just checking to avoid trial-and-error, as it was a surprise to me in the first place that testing migration doesn't consider Provides. There are no versioned provides, so php5-common doesn't satisfy the php5-mhash (= 5.2.0) dependency. Cheers, Julien signature.asc Description: Digital signature
Re: simplesamlphp not migrating to testing
On 2010-06-27 19:36 +0200, Thijs Kinkhorst wrote: On snein 27 Juny 2010, Julien Cristau wrote: My package simplesamlphp is not migrating to testing: Excuse for simplesamlphp * 23 days old (needed 10 days) * simplesamlphp/i386 unsatisfiable Depends: php5-mhash (= 5.2.0) * Valid candidate In squeeze php5-mhash is provided by php5, in Lenny this is a separate package. I want to Depend on php5-mhash to also keep the dependencies correct in a Lenny context. What can I do to have the package migrate? Change the Depends to php5 (= $whatever) | php5-mhash? OK, I will do that but I'm just checking to avoid trial-and-error, as it was a surprise to me in the first place that testing migration doesn't consider Provides. Huh? Versioned Provides have never been supported, so simplesamlphp is simply not installable in sid. Sven -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bpawpdx8@turtle.gmx.de
Re: simplesamlphp not migrating to testing
On snein 27 Juny 2010, Sven Joachim wrote: On 2010-06-27 19:36 +0200, Thijs Kinkhorst wrote: On snein 27 Juny 2010, Julien Cristau wrote: My package simplesamlphp is not migrating to testing: Excuse for simplesamlphp * 23 days old (needed 10 days) * simplesamlphp/i386 unsatisfiable Depends: php5-mhash (= 5.2.0) * Valid candidate In squeeze php5-mhash is provided by php5, in Lenny this is a separate package. I want to Depend on php5-mhash to also keep the dependencies correct in a Lenny context. What can I do to have the package migrate? Change the Depends to php5 (= $whatever) | php5-mhash? OK, I will do that but I'm just checking to avoid trial-and-error, as it was a surprise to me in the first place that testing migration doesn't consider Provides. Huh? Versioned Provides have never been supported, so simplesamlphp is simply not installable in sid. Hmm, you are right. As it seems I added the version spec last minute before uploading. I'll just remove it again then, since oldstable and up have at least 5.2.0. Cheers, Thijs signature.asc Description: This is a digitally signed message part.
NEW changes in proposedupdates
Processing changes file: pango1.0_1.20.5-6_amd64.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_amd64.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_alpha.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_arm.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_armel.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_hppa.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_i386.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_ia64.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_mips.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_mipsel.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_powerpc.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_s390.changes ACCEPT Processing changes file: xulrunner_1.9.0.19-2_sparc.changes ACCEPT Processing changes file: kvirc_3.4.0-5_i386.changes ACCEPT Processing changes file: kvirc_3.4.0-5_alpha.changes ACCEPT Processing changes file: kvirc_3.4.0-5_amd64.changes ACCEPT Processing changes file: kvirc_3.4.0-5_arm.changes ACCEPT Processing changes file: kvirc_3.4.0-5_armel.changes ACCEPT Processing changes file: kvirc_3.4.0-5_hppa.changes ACCEPT Processing changes file: kvirc_3.4.0-5_ia64.changes ACCEPT Processing changes file: kvirc_3.4.0-5_mips.changes ACCEPT Processing changes file: kvirc_3.4.0-5_mipsel.changes ACCEPT Processing changes file: kvirc_3.4.0-5_powerpc.changes ACCEPT Processing changes file: kvirc_3.4.0-5_s390.changes ACCEPT Processing changes file: kvirc_3.4.0-5_sparc.changes ACCEPT -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1ot3wg-00035l...@ries.debian.org
