Processed: block 708536 with 710545
Processing commands for cont...@bugs.debian.org: > block 708536 with 710545 Bug #708536 [release.debian.org] transition: python3-defaults (add python3.3 to supported python3) 708536 was blocked by: 712014 711926 692381 707315 708011 711761 708536 was not blocking any bugs. Added blocking bug(s) of 708536: 710545 > thanks Stopping processing here. Please contact me if you need assistance. -- 708536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13716093121394.transcr...@bugs.debian.org
Re: Current and upcoming toolchain changes for jessie
Hi Aurelien, On 18-Jun-13, at 6:05 PM, Aurelien Jarno wrote: This is true that they have recently contacted me through another email address, but I haven't found time to work on that. Just stay tuned. That's great news. Helge and I have been working away as best we can to maintain the port. I know everybody is busy and this is a significant effort. Dave -- John David Anglin dave.ang...@bell.net -- 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/blu0-smtp54755f6f47f39a181d6a697...@phx.gbl
Re: Current and upcoming toolchain changes for jessie
On Fri, Jun 14, 2013 at 01:12:30PM +0200, Matthias Klose wrote:
> Am 13.06.2013 16:46, schrieb Steven Chamberlain:
> > Hi,
> >
> > On 13/06/13 13:51, Matthias Klose wrote:
> >> GCC 4.8 is now the default on all x86 architectures, and on all ARM
> >> architectures (the latter confirmed by the Debian ARM porters). I did not
> >> get
> >> any feedback from other port maintainers, so unless this does change and
> >> port
> >> maintainers get involved with toolchain maintenance, the architectures
> >> staying
> >> at 4.6 or 4.7 shouldn't be considered for a successful release
> >> (re-)qualification.
> >
> > I trust these are the architectures that are okay so far:
> > | gcc48_archs = amd64 armel armhf arm64 i386 x32 kfreebsd-amd64
> > kfreebsd-i386 hurd-i386
>
> no, they are probably not ok, and there surely are yet undiscovered
> regressions,
> but at least the ARM porters did agree to address these. Same seems to be true
> for the kfreebsd and hurd porters. They did change GCC defaults usually at the
> same time as this was done for the x86 linux archs.
>
> > So the following would be the architectures for which some response is
> > requested urgently from port maintainers, to confirm they are ready for
> > GCC 4.8 as default:
> >
> > Release arches: ia64 mips mipsel powerpc s390 s390x sparc
> >
> > All the above have built gcc-4.8.1-2 or higher.
>
> and nobody committing to scan the bts for architecture specific issues, nobody
> to prepare test cases, nobody to forward these.
I did report a few mips/mipsel issue to upstream binutils and gcc, and
they have all been solved. I am not aware of any reported mips/mipsel
binutils or gcc-4.{6,7,8} problem reported in the debian BTS, except
#710683, which is recent and I haven't investigated it yet (but is likely
an OOM issue on the buildd).
Could you please provide me a few pointers?
> > Other ports: alpha hppa* m68k powerpcspe ppc64 sh4* sparc64*
> >
> > * these ports don't appear to have successfully built GCC 4.8 yet.
>
> afaics, alpha, powerpcspe and ppc64 did build. Note that you cannot trust the
> hppa status, this port is still denied access to ports.debian.org and is kept
> in
> another place.
>
hppa porters have ignored my emails during a few years, and then started
to write me during a few more years using an email address that went
to /dev/null, so they never got my answers, and thus never answered me...
This is true that they have recently contacted me through another email
address, but I haven't found time to work on that. Just stay tuned.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net
--
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/20130618220536.ga22...@hall.aurel32.net
Bug#712725: pu: package espeak/1.43.03-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: pu Hello, A user reported that “using espeak as an emacspeak speech server is basically unusable if you're using pulse, which is kind of the default configuration in wheezy.” (Bug#712629). This happens because the last chunk of the synthesized sample gets lost. A simple solution was found by forcing a flush, see patch below. Would it be OK to upload to wheezy? Samuel Description: Trigger speech start on final chunk of write When espeak is used with pulseaudio, the last part of a line or other chunk is not spoken because pa_stream_trigger needs to get called to start speech. This is called if the buffer is full and writes are not progressing. However nothing calls this for the last part of what's being spoken. The contract for wave_write on the portaudio side seems to start the stream, so do the same on pulse. This patch takes advantage of the fact that calling pulse_free twice in a row with no write causes a trigger. An alternative but larger change would be to refactor that code out of pulse_free. Author: Sam hartman --- The information above should follow the Patch Tagging Guidelines, please checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here are templates for supplementary fields that you might want to add: --- espeak-1.46.02.orig/src/wave_pulse.cpp +++ espeak-1.46.02/src/wave_pulse.cpp @@ -731,6 +731,9 @@ size_t wave_write(void* theHandler, char } pulse_write(aBuffer, bytes_to_write); + //trigger + aTotalFreeMem = pulse_free(); + aTotalFreeMem = pulse_free(); terminate: pthread_mutex_unlock(&pulse_mutex); -- 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/20130618203004.ga23...@type.youpi.perso.aquilenet.fr
Bug#712622: pu: package wv2/0.4.2.dfsg.1-9.1
Control: severity -1 normal
Control: tags -1 + wheezy moreinfo
On Tue, 2013-06-18 at 11:23 +1200, Olly Betts wrote:
> Package: release.debian.org
> Severity: serious
Nope. It's an RC bug in wv2, the request to update that package is
normal at most.
> README.Debian says that src/generator/generator_wword{6,8}.htm have been
> removed from the repacked wv2_0.4.2.dfsg.1.orig.tar.bz2, but they are
> still present.
>
> These two files are based on documents copyright Microsoft. I can't see
> a clear licence statement, but it seems unlikely their licence would fit
> the DFSG or that talking to Microsoft would get them released under such
> a licence.
What version were you proposing to use for the re-repack?
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/137157.29498.4.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#712622: pu: package wv2/0.4.2.dfsg.1-9.1
Processing control commands: > severity -1 normal Bug #712622 [release.debian.org] pu: package wv2/0.4.2.dfsg.1-9.1 Severity set to 'normal' from 'serious' > tags -1 + wheezy moreinfo Bug #712622 [release.debian.org] pu: package wv2/0.4.2.dfsg.1-9.1 Added tag(s) wheezy and moreinfo. -- 712622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b712622.137158001019253.transcr...@bugs.debian.org
Bug#712623: opu: package wv2/0.4.2.dfsg.1-1
Control: tags -1 + moreinfo squeeze
Control: severity -1 normal
On Tue, 2013-06-18 at 11:32 +1200, Olly Betts wrote:
> Package: release.debian.org
> Severity: serious
As with #712622, no, it's not.
> README.Debian says that src/generator/generator_wword{6,8}.htm have been
> removed from the repacked wv2_0.4.2.dfsg.1.orig.tar.bz2, but they are
> still present.
And the same question as for the wheezy bug - what's the suggested
version for the new package?
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/1371580185.29498.7.ca...@jacala.jungle.funky-badger.org
Processed: Re: Bug#712623: opu: package wv2/0.4.2.dfsg.1-1
Processing control commands: > tags -1 + moreinfo squeeze Bug #712623 [release.debian.org] opu: package wv2/0.4.2.dfsg.1-1 Added tag(s) squeeze and moreinfo. > severity -1 normal Bug #712623 [release.debian.org] opu: package wv2/0.4.2.dfsg.1-1 Severity set to 'normal' from 'serious' -- 712623: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712623 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.b712623.137158019320346.transcr...@bugs.debian.org
Bug#712688: transition: gdal
On Tue, Jun 18, 2013 at 04:27:41PM +0200, Francesco Paolo Lovergine wrote: > BTW, without annoying all of you with a so looong history about > this issue, I'm going to introduce a new libgdal1h binary package (h means > hidden, better > suggestions are welcome :)), with a new SONAME libgdal.1h to manage a decent > migration > to the new flavor. This will sacrifice third-parties sw compatibility, but > well, who cares? It would be break anyway. > Maybe a better choice in this specific case would be introducing a new binary package (libgdal1h) that Conflicts/Breaks against libgdal1 and provides the usual library with the usual name/soname. Of course, that will force a lot of bNMUs and an explicit unblocking set to complete the transition properly. Make sense? -- Francesco P. Lovergine -- 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/20130618151603.gh5...@blegrez.ba.issia.cnr.it
Bug#712688: transition: gdal
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition Dear RMs I'm going to provide a long due change to gdal library (current 1.9.0) in sid. In order to solve properly problems of programs that both link geotiff, tiff and gdal libraries, I'm going to drop direct tiff/geotiff functions providing. Upstreams provide now a renaming feature for that (note that the internal gdal version indeed use a bit different ABI) and the result will be a bit different API/ABI starting from next 1.10.0 version. (See http://wiki.orfeo-toolbox.org/index.php/Link_conflicts about that and the partially working fix of #558733) Unfortunately, upstreams do not consider that a true API change (in some way the use of geotiff/tiff funcs out of the gdal interface is considered de facto a deprecated use). So the official upstream soname is indeed the same. BTW, without annoying all of you with a so looong history about this issue, I'm going to introduce a new libgdal1h binary package (h means hidden, better suggestions are welcome :)), with a new SONAME libgdal.1h to manage a decent migration to the new flavor. This will sacrifice third-parties sw compatibility, but well, who cares? It would be break anyway. That could also imply that some r-deps will have to explicitly link now tiff/geotiff libraries instead of using the gdal inner one. As usual I will start all the transition in experimental ASAP. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.9-1-686-pae (SMP w/1 CPU core) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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/20130618142741.18677.54491.report...@blegrez.ba.issia.cnr.it
Re: Bug#706866: transition: libarchive
On Sun, Jun 16, 2013 at 08:45:17PM +0200, Julien Cristau wrote: > On Sun, Jun 16, 2013 at 12:39:28 -0400, Andres Mejia wrote: > > > I see the packages were built on the last two archs after retrying. > > The packages have been built on all archs now. > > > Yes, the blockers now are #701606 (rdup FTBFS), #666834 > (libapache-mod-musicindex), and #711544 (claws-mail FTBFS). > Plus libsoup2.4 FTBFS on kfreebsd, which blocks gnome-online-accounts, > which blocks gvfs. FWIW, claws-mail 3.9.2-1 fixing #711544 has been uploaded minutes ago. regards, -- Ricardo Mones ~ Quantity derives from measurement, figures from quantities, comparisons from figures, and victories from comparisons. Sun Tzu signature.asc Description: Digital signature
