search for: pkgreport

...ph bugzilla may want to look at the urls below. Be sure to check the bugs marked as fixed in NMU since they may have patches that aren't in cvs yet. I'll try to be around to help verify the bugs are fixed before release tomorrow/monday. Thanks, Chris Cheney http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libao http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libogg http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libvorbis http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=vorbis-tools http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pyao http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=pyog...

Looking through http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xen I think it would be useful to add some usertags, in particular to easily filter for toolstack specific (i.e xend) bugs. I think we can use the pkg-xen-devel at lists.alioth.debian.org namespace for this -- what do you think? Ian.

...tag 323698 + pending-in-svn thanks Hi! I'm user-tagging some of the bugs in the bts so we can keep a better track of the status, without actually changing the "official" view in the BTS before we actually upload the package! Tags should be visible at http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=xen&user=pkg-xen-devel@lists.alioth.debian.org Guido

On Fri, Aug 16, 2013 at 03:16:49PM +0100, Ian Campbell wrote: > Looking through http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xen I > think it would be useful to add some usertags, in particular to easily > filter for toolstack specific (i.e xend) bugs. I've never seen the use for this. The kernel team tried and it did not work well. The release team however uses them and like it. >...

...a look at the xen bugs (mostly xen 3.x stuff that was neither reassigned to xen 4 nor closed at the time xen3 was removed) and either reassign them to existing (source) packages or close them. The complete list of bugs in packages w/o maintainer can be found here: https://bugs.debian.org/cgi-bin/pkgreport.cgi?maint= It's difficult to limit this to only packages related to xen since there are so many different xen binary packages ... Thanks Andreas

...I can read about those known issues ? (not found in [1]). 2. For systemd envs where /etc/init.d files are still used, what do you recommend ? 3. For systemd envs where /etc/init.d files are not used anymore, what do you recommend ? 4. Suggestions ? Regards [1] https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=asterisk;dist=unstable -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20170217/d61e876a/attachment.html>

...version, which uses "stable" releases. Each Debian build takes 6 hours, so finding and fixing these bugs one by one is quite a long process. llvm-gcc-4.2-2.5 is failing to build from source on arm, sparc, powerpc and ia64, only succeeding on i386 and amd64: http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=llvm-gcc-4.2;dist=unstable so it looks like the 2.5 release was never properly tested before it was published. If the issues and fixes are "known", can you make them known to the public, for example by producing a 2.5.1 with the worst bugs fixed, or by documenting the issues and...

On Aug 4, 2009, at 5:33 AM, Anton Korobeynikov wrote: > Hello, Martin > >> llvm-gcc-4.2-2.5 is failing to build from source on arm, sparc, >> powerpc and ia64, only succeeding on i386 and amd64: >> http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=llvm-gcc-4.2;dist=unstable >> so it looks like the 2.5 release was never properly tested before it >> was published. > Unfortunately, ia64 and sparc were never considered as a 'tier-1' > targets for llvm-gcc, there was noone who cared about it. Also, our > linux...

...Aug 4, 2009, at 5:33 AM, Anton Korobeynikov wrote: >> >>> Hello, Martin >>> >>>> llvm-gcc-4.2-2.5 is failing to build from source on arm, sparc, >>>> powerpc and ia64, only succeeding on i386 and amd64: >>>> http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=llvm-gcc-4.2;dist=unstable >>>> so it looks like the 2.5 release was never properly tested before >>>> it >>>> was published. >>> Unfortunately, ia64 and sparc were never considered as a 'tier-1' >>> targets for llvm-gcc, there...

...Lattner wrote: > On Aug 4, 2009, at 5:33 AM, Anton Korobeynikov wrote: > >> Hello, Martin >> >>> llvm-gcc-4.2-2.5 is failing to build from source on arm, sparc, >>> powerpc and ia64, only succeeding on i386 and amd64: >>> http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=llvm-gcc-4.2;dist=unstable >>> so it looks like the 2.5 release was never properly tested before it >>> was published. >> Unfortunately, ia64 and sparc were never considered as a 'tier-1' >> targets for llvm-gcc, there was noone who cared about it. Also...

Hello, Martin > llvm-gcc-4.2-2.5 is failing to build from source on arm, sparc, > powerpc and ia64, only succeeding on i386 and amd64: > http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=llvm-gcc-4.2;dist=unstable > so it looks like the 2.5 release was never properly tested before it > was published. Unfortunately, ia64 and sparc were never considered as a 'tier-1' targets for llvm-gcc, there was noone who cared about it. Also, our linux resources are pretty l...

Thanks. Do you have fixes for the other ARM bloopers? This is the forthcoming Debian version and it's now dying on arm-gnueabi when it links cc2-dummy saying libbackend.a(arm.o): In function `current_file_function_operand': /home/martin/arm/llvm-gcc-4.2-2.5/build-gcc/gcc/../../llvm-gcc-4.2-2.5/gcc/config/arm/arm.c:3506: undefined reference to `ENCODED_SHORT_CALL_ATTR_P'

Hello, Martin > Thanks. Do you have fixes for the other ARM bloopers? This is the > forthcoming Debian version and it's now dying on arm-gnueabi when it > links cc2-dummy saying Please use the current Top-of-the-Tree version. I was successfully built cross llvm-gcc for arm-elf / arm-gnu-linux-eabi target triples. -- With best regards, Anton Korobeynikov Faculty of Mathematics and

On Mon, 2013-08-19 at 13:28 +0200, Bastian Blank wrote: > On Fri, Aug 16, 2013 at 03:16:49PM +0100, Ian Campbell wrote: > > Looking through http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xen I > > think it would be useful to add some usertags, in particular to easily > > filter for toolstack specific (i.e xend) bugs. > > I've never seen the use for this. I was hoping to filter out the many xend bugs in the bts which are clearly never going to get fix...

...ings like endian issues, 32/64 bit processors, and various int/pointer conventions not accounted for by the programmer tend to show up. As I write this, speex has been successfully built on 9 architectures :) Debian also has a bug tracking system (BTS), for speex: http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=speex&repeatmerged=yes There is also a status page: http://packages.qa.debian.org/s/speex.html (If this does not work yet, try later.) Note that the Debian Package Tracking System (PTS) also has an email subscription available from that overview page. Information on the PTS is at...

...of Speex</a></li> <li><a href="http://ftp.debian.org/debian/pool/main/s/speex/">Package Pool for Speex</a> - all available Debian versions.</li> <li><a href="http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=speex"> Debian bug report log for Speex</a></li> </ul> </dd> <p>-Maitland --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, sen...

...+0200, Stefan Strasser wrote: > in case you're interested in having llvm in debian sarge: it was > removed today. I don't know why, but you might want to find out > because sarge is in freeze phase for release next month. Possibly because of these: http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=llvm I addressed the first one and fixed it in CVS -- LLVM used to produce an executable named `extract' which conflicted with another program of the same name; I renamed ours to `llvm-extract'. However, they are building the .deb from 1.4, so the patch didn't make it nor were...

in case you're interested in having llvm in debian sarge: it was removed today. I don't know why, but you might want to find out because sarge is in freeze phase for release next month. regards, -- Stefan Strasser

Hi, I'd like to announce Speex beta 3: This is the third beta for Speex, implementing what should be the last new features before 1.0. These new features are a new "ultra-wideband" mode for encoding at 32 kHz (up to 48 kHz) and an intensity stereo mode. Both of these are implemented to preserve both backward and forward compatibility with other releases. This means that it is now

...tner skrev: > > On Aug 4, 2009, at 5:33 AM, Anton Korobeynikov wrote: > >> Hello, Martin >> >>> llvm-gcc-4.2-2.5 is failing to build from source on arm, sparc, >>> powerpc and ia64, only succeeding on i386 and amd64: >>> http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=llvm-gcc-4.2;dist=unstable >>> so it looks like the 2.5 release was never properly tested before it >>> was published. >> Unfortunately, ia64 and sparc were never considered as a 'tier-1' >> targets for llvm-gcc, there was noone who cared about it. Also...