Processed: raising severity for bug reports which fail to build with GCC-4.4 (now the default)
- To: Matthias Klose <doko@debian.org>
- Cc: Alexander Sack <asac@debian.org> (iceowl for {505353}), Adam Majer <adamm@zombino.com> (mysql-gui-tools for {505677}), brlink@debian.org (Bernhard R. Link) (cuyo for {504947}), Noèl Köthe <noel@debian.org> (hammerhead for {505076}), Tomasz Mrugalski <thomson@klub.com.pl> (dibbler for {504901}), Debian Telepathy maintainers <pkg-telepathy-maintainers@lists.alioth.debian.org> (libjingle0.3 for {505699}), Peter Eisentraut <petere@debian.org> (kmldonkey for {525752}), Ubuntu Mozilla Team <ubuntu-mozillateam@lists.ubuntu.com> (icedove for {505352}), Zhengpeng Hou <zhengpeng-hou@ubuntu.com> (scim-bridge for {504869}), Debian Boost Team <pkg-boost-devel@lists.alioth.debian.org> (boost1.35 for {505109}), unknown-package@qa.debian.org (glashctl for {504937}), Loic Dachary (OuoU) <loic@debian.org> (jaula for {526207}), Loic Minier <lool@dooz.org> (libglib2.0-dev for {547400}), Gürkan Sengün <gurkan@phys.ethz.ch> (traverso for {505390}, mm3d for {505626}), Arthur Loiret <arthur.loiret@gmail.com> (audiere for {505122}), David Martínez Moreno <ender@debian.org> (aqsis for {504858}), Colin Watson <cjwatson@debian.org> (putty for {526670}), Francis Tyers <ftyers@prompsit.com> (apertium for {505356}), Maintainers of Mozilla-related packages <pkg-mozilla-maintainers@lists.alioth.debian.org> (iceape for {505599}), Daniel Burrows <dburrows@debian.org> (aptitude for {531687}), Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> (koffice for {504870}), Experimental Psychology Maintainers <pkg-exppsy-maintainers@lists.alioth.debian.org> (odin for {553708}), Peter Miller <pmiller@opensource.org.au> (libexplain for {541174}), Jeremy Lainé <jeremy.laine@m4x.org> (kdevelop for {546961}), Pierre Machard <pmachard@debian.org> (cryptonit for {504980})
- Subject: Processed: raising severity for bug reports which fail to build with GCC-4.4 (now the default)
- From: owner@bugs.debian.org (Debian Bug Tracking System)
- Date: Sun, 10 Jan 2010 15:57:38 +0000
- Message-id: <[🔎] handler.s.C.126313867116967.transcript@bugs.debian.org>
- In-reply-to: <4B49F747.3060102@debian.org>
- References: <4B49F747.3060102@debian.org>
Processing commands for control@bugs.debian.org:
> severity 505109 serious
Bug #505109 [boost1.35] FTBFS with GCC 4.4 and breaks other apps
Severity set to 'serious' from 'important'
> severity 547400 serious
Bug #547400 [libglib2.0-dev] Causes FTBFS with GCC 4.4: dereferencing pointer '_SOUP_..' breaks strict-aliasing rules
Severity set to 'serious' from 'important'
> severity 504858 serious
Bug #504858 [aqsis] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 504869 serious
Bug #504869 [scim-bridge] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 504870 serious
Bug #504870 [koffice] FTBFS with GCC 4.4: #elif used instead of #else
Severity set to 'serious' from 'normal'
> severity 504901 serious
Bug #504901 [dibbler] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 504980 serious
Bug #504980 [cryptonit] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 505122 serious
Bug #505122 [audiere] FTBFS with GCC 4.4: missing #include, and other problems
Severity set to 'serious' from 'normal'
> severity 505356 serious
Bug #505356 [apertium] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 505390 serious
Bug #505390 [traverso] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 505626 serious
Bug #505626 [mm3d] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 505677 serious
Bug #505677 [mysql-gui-tools] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 525752 serious
Bug #525752 [kmldonkey] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 526207 serious
Bug #526207 [jaula] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 531687 serious
Bug #531687 [aptitude] aptitude: [patch] gcc4.4 build fixes
Severity set to 'serious' from 'normal'
> severity 553708 serious
Bug #553708 [odin] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 504937 serious
Bug #504937 [glashctl] FTBFS with GCC 4.4: missing #include, conflicting declaration 'char*** argv'
Warning: Unknown package 'glashctl'
Severity set to 'serious' from 'normal'
Warning: Unknown package 'glashctl'
> severity 505352 serious
Bug #505352 [icedove] FTBFS with GCC 4.4: 'virtual nsIOThreadPool::~nsIOThreadPool()' is private
Severity set to 'serious' from 'normal'
> severity 505353 serious
Bug #505353 [iceowl] FTBFS with GCC 4.4: 'virtual nsIOThreadPool::~nsIOThreadPool()' is private
Severity set to 'serious' from 'normal'
> severity 505599 serious
Bug #505599 [iceape] FTBFS with GCC 4.4: 'virtual nsIOThreadPool::~nsIOThreadPool()' is private
Severity set to 'serious' from 'normal'
> severity 526670 serious
Bug #526670 [putty] FTBFS with GCC 4.4: dereferencing pointer breaks strict-aliasing rules
Severity set to 'serious' from 'normal'
> severity 541174 serious
Bug #541174 [libexplain] FTBFS with GCC 4.4: dereferencing pointer 'sa' does break strict-aliasing rules
Severity set to 'serious' from 'normal'
> severity 546961 serious
Bug #546961 [kdevelop] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 504947 serious
Bug #504947 [cuyo] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'important'
> severity 505076 serious
Bug #505076 [hammerhead] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> severity 505699 serious
Bug #505699 [libjingle0.3] FTBFS with GCC 4.4: missing #include
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
Reply to: