Please hint libdatetime-locale-perl, libdatetime-format-strptime-perl
Hi, libdatetime-locale-perl breaks libdatetime-format-strptime-perl currently in testing and *-strptime-perl depends on the new version of *-locale-perl in unstable. I think they need to be hinted in this case: hint libdatetime-format-strptime-perl/1.2000-1 libdatetime-locale-perl/1:0.45-1 Regards, Ansgar -- 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/87ljd38ncm@marvin.43-1.org
Re: Please hint libdatetime-locale-perl, libdatetime-format-strptime-perl
Hi, On Sun, April 4, 2010 12:32, Ansgar Burchardt wrote: libdatetime-locale-perl breaks libdatetime-format-strptime-perl currently in testing and *-strptime-perl depends on the new version of *-locale-perl in unstable. I think they need to be hinted in this case: Easy hint added. Regards, Adam -- 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/17d30e1677063fdbd92d9981923578d6.squir...@adsl.funkybadger.org
Bug#576439: transition: ocsigen, nurpawiki
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition easy ocsigen/1.3.0-4 nurpawiki/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-4-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/20100404171006.28437.5259.report...@korell.glondu.net
squeeze release-notes (was: Invite to join the Release Team)
On Thu, Mar 18, 2010 at 07:19:19PM +0100, Simon Paillard wrote: On Thu, Mar 18, 2010 at 08:35:05AM +0100, Raphael Hertzog wrote: On Wed, 17 Mar 2010, Marc 'HE' Brockschmidt wrote: The release notes need to be updated for squeeze and upgrade and installation tests on different configurations should be organized. It's a bit early to do it, as many components of squeeze are not done yet, but at least finding people who would be interested in working on this would be great. [..] http://bugs.debian.org/release-notes What we've observed from lenny releease-notes that there were quite few reports from maintainers, so IMO we should remind them soon to report major changes in behaviour/config to RN (and NEWS.Debian). Getting and reading a lenny - squeeze diff of all the NEWS.Debian would be a start (though it may be a too exhaustive method). http://lintian.debian.org/~spaillard/lenny-squeeze-NEWS.diff/ (Not cronned, extracted from *source* packages from lintian laboratory that match debian/*NEWS*) That could be done per user basis *before* upgrade to squeeze, see #419201 on packages.d.o to providing the NEWS file, #525803 on aptitude to using it once available. That will be processed again against binary files, since nothing ensures the location or name of the NEWS file in the source packge. - Some of these NEWS file contents describe workarounds without details/commands. - There are 423 such NEWS diffs, they need to be reviewed so that only ( high popcon x impact ) are documented in RN. Questions: 1/ In case someone noticed lacks in NEWS file, would the RT allow migration to testing after freeze only for NEWS file update ? 2/ Is it acceptable to change NEWS log entry a posteriori ? 3/ Other comments ? Regards. -- Simon Paillard -- 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/20100404183801.gb1...@dedibox.ebzao.info
Bug#576439: marked as done (transition: ocsigen, nurpawiki)
Your message dated Sun, 4 Apr 2010 19:16:02 +0100 with message-id 34f3761365bd3670dfcce033e9ea7786.squir...@adsl.funkybadger.org and subject line Re: Bug#576439: transition: ocsigen, nurpawiki has caused the Debian Bug report #576439, regarding transition: ocsigen, nurpawiki to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 576439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition easy ocsigen/1.3.0-4 nurpawiki/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-4-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 ---End Message--- ---BeginMessage--- On Sun, April 4, 2010 18:10, Stéphane Glondu wrote: easy ocsigen/1.3.0-4 nurpawiki/1.2.3-4 Added; thanks. Regards, Adam ---End Message---
Re: squeeze release-notes (was: Invite to join the Release Team)
* Simon Paillard (spaill...@debian.org) [100404 20:38]: 1/ In case someone noticed lacks in NEWS file, would the RT allow migration to testing after freeze only for NEWS file update ? Depends on how long the freeze will probably take, but as long as we allow to migrate for l10n-upgrades, NEWS-files sounds sane to me. 2/ Is it acceptable to change NEWS log entry a posteriori ? why not (it might get difficult after the first mass-upgrades happens, but that's nothing that will happen as of tomorrow). 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/20100404193503.gm19...@mails.so.argh.org
Add support new architecture
Hi, Release team.
I am now trying to run Debian [0] on Renesas SH(sh4) CPU[1].
The sh4 packages increase and can use it apart from some problem packages.
I want to put a sh4 support in squeeze+1.
# In fact, I want to put it in squeeze.
I want to get ready to be able to release sh4 by the squeeze+1.
What is necessary so that we make sh4 the official architecture?
If there is the item which we should confirm, please teach it.
Best regards,
Nobuhiro
[0]: http://buildd.debian-ports.org/status/architecture.php?suite=unstablea=sh4
[1]: http://en.wikipedia.org/wiki/SuperH
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
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/y2p29ab51dc1004042023pe05fe6c9x6c4f43a1df77a...@mail.gmail.com
Re: Add support new architecture
I'm not a member of the release team, but hopefully I can point you at some docs and save the release team doing so. There are two separate criteria to be satisfied: The archive criteria, for getting the arch supported in testing/sid and available from the official archive and Debian mirrors. The release criteria, for getting the arch supported in stable and blocking package testing transitions where there is a bug. Some links on these are below. Arch archive criteria: http://ftp-master.debian.org/archive-criteria.html Arch archive qualifications for other unofficial ports: http://wiki.debian.org/ArchiveQualification/arm http://wiki.debian.org/ArchiveQualification/hurd-i386 http://wiki.debian.org/ArchiveQualification/kfreebsd-amd64 http://wiki.debian.org/ArchiveQualification/kfreebsd-i386 http://wiki.debian.org/ArchiveQualification/m68k Arch release criteria (looks to be a copy of the lenny one): http://release.debian.org/squeeze/arch_policy.html Current arch release status for squeeze: http://release.debian.org/squeeze/arch_qualify.html Arch release qualifications for lenny: http://wiki.debian.org/CategoryLennyReleaseRecertification There is probably more, like Debian will need porter and buildd machines, administered by DSA. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/m2te13a36b31004042142ob7f23d00qeaedfd9ca5d55...@mail.gmail.com
Re: Add support new architecture
Hi, Paul.
2010/4/5 Paul Wise p...@debian.org:
I'm not a member of the release team, but hopefully I can point you at
some docs and save the release team doing so.
There are two separate criteria to be satisfied:
The archive criteria, for getting the arch supported in testing/sid
and available from the official archive and Debian mirrors.
The release criteria, for getting the arch supported in stable and
blocking package testing transitions where there is a bug.
Some links on these are below.
Arch archive criteria:
http://ftp-master.debian.org/archive-criteria.html
Arch archive qualifications for other unofficial ports:
http://wiki.debian.org/ArchiveQualification/arm
http://wiki.debian.org/ArchiveQualification/hurd-i386
http://wiki.debian.org/ArchiveQualification/kfreebsd-amd64
http://wiki.debian.org/ArchiveQualification/kfreebsd-i386
http://wiki.debian.org/ArchiveQualification/m68k
Arch release criteria (looks to be a copy of the lenny one):
http://release.debian.org/squeeze/arch_policy.html
Current arch release status for squeeze:
http://release.debian.org/squeeze/arch_qualify.html
Arch release qualifications for lenny:
http://wiki.debian.org/CategoryLennyReleaseRecertification
There is probably more, like Debian will need porter and buildd
machines, administered by DSA.
The information that I wanted is these.
Thank you!
Best regards,
Nobuhiro
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
--
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/t2r29ab51dc1004042147n7eee62deh296d411f47fa8...@mail.gmail.com
Bug#576487: nmu: All packages which depend on libao-dev
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu Hi, Upstream has recently released a new version of libao which required a soname bump. nmu aldo/0.7.5-1 . ALL . -m Rebuild against new libao nmu cdrdao/1:1.2.2-18.1 . ALL . -m Rebuild against new libao nmu cmus/2.2.0-4.1 . ALL . -m Rebuild against new libao nmu gnomoradio/0.15.1-5.3 . ALL . -m Rebuild against new libao nmu kadu/0.6.5.4-1 . ALL . -m Rebuild against new libao nmu ocaml-ao/0.1.10-2 . ALL . -m Rebuild against new libao nmu liquidsoap/0.9.2-2 . ALL . -m Rebuild against new libao nmu mpc123/0.2.4-1.1 . ALL . -m Rebuild against new libao nmu mpd/0.15.9-1 . ALL . -m Rebuild against new libao nmu mpg321/1.10.0-2 . ALL . -m Rebuild against new libao nmu nateon/1.0.1.248-1 . ALL . -m Rebuild against new libao nmu potamus/0.10-1 . ALL . -m Rebuild against new libao nmu python-pyao/0.82-2.1 . ALL . -m Rebuild against new libao nmu pytone/3.0.0-1 . ALL . -m Rebuild against new libao nmu shell-fm/0.4+svn20071125.r282-1 . ALL . -m Rebuild against new libao nmu somaplayer/0.5.2.1.ds-1.1 . ALL . -m Rebuild against new libao nmu sox/14.3.0-1.1 . ALL . -m Rebuild against new libao nmu upse123/0.6.0-1 . ALL . -m Rebuild against new libao nmu yatm/0.6-1 . ALL . -m Rebuild against new libao nmu ydpdict/1.0.0-1 . ALL . -m Rebuild against new libao nmu zsnes/1.510-2.2 . ALL . -m Rebuild against new libao -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.31-20-generic (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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/20100405045903.10590.46570.report...@zoot.inodes.org
