First Noble Numbat test rebuild
The first test rebuild of Noble Numbat was started on December 15, 2023 for all architectures, all components. The rebuild is finished for all architectures for the main component and still running for universe and multiverse on s390x and riscv64. There were some buildd issues with s390x, but we hope they will catch up soon. Results (please also look at the superseded builds) can be found at: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-noble.html Additional build failures for packages in noble-proposed (not yet in noble) can be found at: http://qa.ubuntuwire.com/ftbfs/ Please help with fixing the build failures. Another test rebuild using a glibc snapshot from December 2023 can be found at: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-glibc-noble.html Still running for universe and multiverse on s390x and riscv64. The glibc snapshot can be found in: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/glibc Yet another test rebuild using GCC 14 can be found at: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20231215-noble-gcc-noble.html Still running for universe and multiverse on s390x and riscv64. This is in preparation for GCC 14 for the 24.10 release. GCC test packages can be found in: https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test Happy New Year and bug fixing! Graham -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Mantic Minotaur test rebuild
The first test rebuild of Mantic Minotaur was started on August 30, 2023 for all architectures, all components. The rebuild is finished for the main component on all architectures except riscv64, and still running for universe and multiverse. Results (please also look at the superseded builds) can be found at: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230830-mantic-mantic.html Additional build failures for packages in mantic-proposed (not yet in mantic) can be found at: http://qa.ubuntuwire.com/ftbfs/ Please help with fixing the build failures. Graham -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Lunar Lobster test rebuild
The second test rebuild of Lunar Lobster was started on March 24, 2023 for all architectures, all components. The rebuild is finished for the main component on all architectures except riscv64, and still running for universe/multiverse. Results (please also look at the superseded builds) can be found at: https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20230324-lunar-lunar.html Additional build failures for packages in lunar-proposed (not yet migrated to lunar) can be found at: http://qa.ubuntuwire.com/ftbfs/ Please help with fixing the build failures. Graham -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Lunar Lobster test rebuild
The first test rebuild of Lunar Lobster was started on December 15, 2022 for all architectures, all components. The rebuild is finished for all architectures for the main component and still running for universe and multiverse on riscv64. Thanks to everybody keeping the buildds going during the end-of-year break. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-normal-lunar.html Additional build failures for packages in lunar-proposed (not yet in lunar) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help with fixing the build failures. Happy New Year and bug fixing! Graham -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Kinetic Kudu test rebuild
The second test rebuild of Kinetic Kudu was started on September 14, 2022 for all architectures, all components. The rebuild is finished for the main component on all architectures, finished for universe/multiverse on amd64, i386 and ppc64el, and still running on the other architectures. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220914-kinetic-kinetic.html Additional build failures for packages in kinetic-proposed (not yet migrated to kinetic) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Graham -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Kinetic Kudu test rebuild
The first test rebuild of Kinetic Kudu was started on June 17, 2022 for all architectures, all components. The rebuild is finished for all architectures for the main component and still running for universe and multiverse. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220617-kinetic-kinetic.html Additional build failures for packages in kinetic-proposed (not yet in kinetic) can be found at http://qa.ubuntuwire.com/ftbfs/ Another test rebuild using GCC 12 can be found at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220617-kinetic-gcc12-kinetic.html Still running for universe and multiverse. This is in preparation for GCC 12 becoming the default later this cycle. Please help fixing the build failures. Graham -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Second Jammy Jellyfish test rebuild
On Fri, Mar 25, 2022 at 3:24 PM Graham Inggs wrote: > > The latest report, dated 2022-03-25 14:05:01 UTC, no longer has broken > links to build logs that do not exist. Instead, '!Log' is shown for > these. Hi Graham, we've resolved all of our issues by now. I do not know if you need to get your list trimmed down, after all that will need you to build things again and sometimes resources are scarce. So this is an FYI for you if you want/need to trim the list via rebuilds/refreshes/deletions-form-your-ppa. We initially had more and fixed a few, but the currently remaining list holds 5 entries left for the server team: - Dns-root-data is actually an issue in ldns fixed in jammy-proposed by ldns https://launchpad.net/ubuntu/+source/ldns/1.7.1-2ubuntu4 You could consider a rebuild against proposed to get this one green. - postgresql-14 was broken by llvm-14, a fix is uploaded to jammy and built fine (https://launchpad.net/bugs/1966319) You can rebuild the very same, or if you have a less-overhead way to do it just consider this one as done. - python-tempita was broken by python-3.10, not yet fixed but we know a way - Note it’s an openstack package - not server anymore, but we wanted to fix it anyway. - https://launchpad.net/bugs/1966323 - https://bugs.launchpad.net/ubuntu/+source/python-tempita/+bug/1966532 - https://code.launchpad.net/~ahasenack/ubuntu/+source/python-tempita/+git/python-tempita/+merge/417740 - samba shows to build fine in the latter 0ubuntu4 - https://launchpad.net/ubuntu/+source/samba/2:4.15.5~dfsg-0ubuntu4 - consider to remove or rebuild it yourself to pick it up - Mysql is one of the !log cases - we didn't want to trigger a rebuild on our side just to ask you to do one again (wasted time) - instead could you please just rebuild that in your ppa as it should actually be good already I know I said 5, but as a bonus: - Ruby-rexml is fixed for a few days already before the report was sent. Please consider rebuilding all orange ruby* packages (reference LP: #1966201). -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Second Jammy Jellyfish test rebuild
Hi Christian On Tue, 29 Mar 2022 at 08:19, Christian Ehrhardt wrote: > - Dns-root-data is actually an issue in ldns fixed in jammy-proposed ldns migrated, so I retried dns-root-data > - postgresql-14 was broken by llvm-14, a fix is uploaded to jammy and > built fine (https://launchpad.net/bugs/1966319) llvm-toolchain-14 migrated, so I retried postgresql-14 > - python-tempita was broken by python-3.10, not yet fixed but we know a way not doing anything here yet > - samba shows to build fine in the latter 0ubuntu4 samba should move to the superseded section once it migrates > - Mysql is one of the !log cases this seems to have been cleared by my previous retries > - Ruby-rexml is fixed for a few days already before the report was sent. > Please consider rebuilding all orange ruby* packages (reference LP: > #1966201). retrying... Regards Graham -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Second Jammy Jellyfish test rebuild
On Tue, Mar 29, 2022 at 8:02 AM Graham Inggs wrote: > > Hi Christian > > On Tue, 29 Mar 2022 at 08:19, Christian Ehrhardt > wrote: > > - Dns-root-data is actually an issue in ldns fixed in jammy-proposed > ldns migrated, so I retried dns-root-data > > > - postgresql-14 was broken by llvm-14, a fix is uploaded to jammy and > > built fine (https://launchpad.net/bugs/1966319) > llvm-toolchain-14 migrated, so I retried postgresql-14 https://launchpad.net/ubuntu/+source/postgresql-14/14.2-1ubuntu1 in proposed fixes the FTBFS with llvm 14. > > > - python-tempita was broken by python-3.10, not yet fixed but we know a way > not doing anything here yet https://launchpad.net/ubuntu/+source/python-tempita/0.5.2-6ubuntu1 is in proposed and fixes the FTBFS (and enables tests, that were not running before) -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Second Jammy Jellyfish test rebuild
On Thu, Mar 24, 2022 at 07:44:11AM -0700, Erich Eickmeyer wrote: > I'm seeing a lot of failed arm64 builds without build logs. In the > past when I've seen this, I've merely retried the build and it has > succeeded. This shows a pattern in that it's likely we've got a buggy > build server. Yeah, this has been reported to us (Launchpad), but for the record we have no handle on a fix at present. The basic symptom is that buildd-manager timed out trying to poll the builder (probably over several attempts). This is either because the builder crashed or hung or something like that (possible under load, and sometimes particular builds will repeatedly OOM a builder or similar), or because of a network failure that meant we lost contact for too long, or because of a buildd-manager bug. Unfortunately it's extremely difficult even for us to tell which at present. Ubuntu test rebuilds tend to exacerbate this sort of thing, because the whole system is under significantly more load than usual. It's something that we'll keep trying to debug, but it's not as simple as a single buggy build machine, and so I want to set expectations that this may not be something we can fix quickly. -- Colin Watson (he/him) [cjwat...@ubuntu.com] -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Second Jammy Jellyfish test rebuild
On Thursday, March 24, 2022 6:05:06 AM PDT Graham Inggs wrote: > The second test rebuild of Jammy Jellyfish was started on March 17, > 2022 for all architectures, all components. The rebuild is finished > for the main component, and finished for universe/multiverse on amd64 > and i386, and still running on the other architectures. > > Results (please also look at the superseded builds) can be found at > > https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220317-jamm > y-jammy.html > > A number of builds failed without logs, and these will be retried. > > Additional build failures for packages in jammy-proposed (not yet > migrated to jammy) can be found at > > http://qa.ubuntuwire.com/ftbfs/ > > Please help fixing the build failures. > > Graham I'm seeing a lot of failed arm64 builds without build logs. In the past when I've seen this, I've merely retried the build and it has succeeded. This shows a pattern in that it's likely we've got a buggy build server. -- Erich Eickmeyer Project Leader - Ubuntu Studio Member - Ubuntu Community Council signature.asc Description: This is a digitally signed message part. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Second Jammy Jellyfish test rebuild
The latest report, dated 2022-03-25 14:05:01 UTC, no longer has broken links to build logs that do not exist. Instead, '!Log' is shown for these. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Jammy Jellyfish test rebuild
The second test rebuild of Jammy Jellyfish was started on March 17, 2022 for all architectures, all components. The rebuild is finished for the main component, and finished for universe/multiverse on amd64 and i386, and still running on the other architectures. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20220317-jammy-jammy.html A number of builds failed without logs, and these will be retried. Additional build failures for packages in jammy-proposed (not yet migrated to jammy) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Graham -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Impish Indri test rebuild
The second test rebuild of Impish Indri was started on September 27 2021 for all architectures, all components. The rebuild is finished for the main component, it's still running for the other components. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20210927-impish-impish.html Additional build failures for packages in impish-proposed (not yet in impish) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Graham -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Impish Indri test rebuild / GCC 11
The first test rebuild of Impish Indri was started on August 05 2021 for all architectures, all components. The rebuild is finished on amd64 and i386 for all components, and finished for all architectures for the main component. Still running for universe and multiverse for non-x86 architectures. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210805-impish-impish.html The rebuild was done with a few packages which are not yet in the impish release pocket. These are: - glibc 2.34 - linux (linux-libc-dev), only in the proposed pocket - golang-defaults pointing to golang-1.17 GCC 11 is now the default compiler; there are no bug reports filed in LP for build failures triggered by GCC 11, however there are reports in the Debian BTS. http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-11;users=debian-...@lists.debian.org Porting advice can be found at https://gcc.gnu.org/gcc-11/porting_to.html The additional packages used for the test rebuild are found in the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile Additional build failures for packages in hirsute-proposed (not yet in hirsute) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Hirsute Hippo test rebuild
The second test rebuild of Hirsute Hippo was started on March 25 2021 for all architectures, all components. The rebuild is finished for the main component, it's still running for the other components. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20210325-hirsute-hirsute.html Additional build failures for packages in hirsute-proposed (not yet in hirsute) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Happy Easter bug/egg hunt, Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Hirsute Hippo test rebuild (and GCC related test rebuilds)
The first test rebuild of Hirsute Hippo was started on December 20 2020 for all architectures, all components. The rebuild is almost finished. It is still running for the multiverse component on some architectures. Thanks to everybody keeping the buildds going during the end-of-year break. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20201216-hirsute-hirsute.html Additional build failures for packages in hirsute-proposed (not yet in hirsute) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using GCC 11 can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20201216-hirsute-gcc11-hirsute.html Still running on arm64, armhf, ppc64el. That's in preparation for GCC 11 for the 21.10 release. GCC test packages can be found in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages Yet another test build turning on link time optimizations by default is at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20201216-hirsute-lto-hirsute.html This is only done for the 64bit architectures amd64, arm64, ppc64el and s390x. The optimizations are turned on by the dpkg package available in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/dpkg-lto/+packages Happy New Year and bug fixing, Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Second Groovy Gorilla test rebuild
On Mon, Sep 28, 2020 at 06:07:08PM +0200, Matthias Klose wrote: > Some build failures on ppc64el and s390x are caused by a buildd issue, and > will > be retried soonish. Please ignore these where you see a ftbfs just on those > architectures, but successes on the other architectures. This should be fixed now. I think I've retried most of the affected builds, though I was doing this manually so it's certainly possible that I missed some. -- Colin Watson (he/him) [cjwat...@ubuntu.com] -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Groovy Gorilla test rebuild
The second test rebuild of Groovy Gorilla was started on September 25 2020 for all architectures, all components. The rebuild is finished for the main component. It is still running for the universe/multiverse components. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200925-groovy-groovy.html Some build failures on ppc64el and s390x are caused by a buildd issue, and will be retried soonish. Please ignore these where you see a ftbfs just on those architectures, but successes on the other architectures. Additional build failures for packages in groovy-proposed (not yet in groovy) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Groovy Gorilla test rebuild
The first test rebuild of Groovy Gorilla was started on July 27 2020 for all architectures (except riscv64), all components. The rebuild is finished for the main component (except for armhf/arm64, still working on some heavy daily PPA test builds). It is still running for the universe/multiverse components. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200728-groovy-groovy.html Additional build failures for packages in groovy-proposed (not yet in groovy) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Focal Fossa test rebuild
The second test rebuild of Focal Fossa was started on March 27 2020 for all architectures, all components. The rebuild is finished for the main component, still running for the universe/multiverse components. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200327-focal-focal.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to eoan. Additional build failures for packages in focal-proposed (not yet in focal) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild with GCC trunk enabled by default. Focal will ship with GCC 10 (as an optional compiler, not the default), and become the default GCC in 20.10. https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20200327-focal-gcc10-focal.html Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Focal Fossa test rebuild
The first test rebuild of Focal Fossa was started on December 20 2019 for all architectures, all components. The rebuild is finished except for some pending universe/multiverse builds on armhf and arm64. A first glance at the test results shows some missing dependencies for i386 builds, and some missing dependencies for Python2 related packages. Please note that the test rebuild is done for the release pocket only. For the first time we have a test rebuild with such a vast amount of packages stuck in the proposed pocket. So besides fixing build failures, please also follow-up on getting packages migrated to the release pocket. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191220-focal-focal.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to eoan. Additional build failures for packages in focal-proposed (not yet in focal) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild with binutils and GCC trunk enabled by default. Focal will ship with binutils 2.34, and GCC 10 (as an optional compiler, not the default). https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191220-focal-gcc10-focal.html Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Eoan Ermine test rebuilds
The second test rebuild of Eoan Ermine was started on September 06 2019 for all architectures, all components. The rebuild of the main component is finished, the other components (restricted, universe, multiverse) are still building. Unfortunately we see 1300+ build failures, and still counting ... On the other hand the test rebuild includes the recent GCC, glibc packages, and the glib2.o/gtk packages synced from experimental. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190906-eoan.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. The test rebuild already uses the linux-libc-dev 5.3 package found in the ubuntu-toolchain-r/volatile PPA. Additional build failures for packages in eoan-proposed (not yet in eoan) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild with link time optimization turned on by default (passing -flto=auto in CFLAGS/CXXFLAGS). Other distributions turned these optimzations on by default, or are considering doing that. https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190906-lto-eoan.html Packages to use -flto by default (dpkg) can be found in the ubuntu-toolchain-r/dpkg-lto PPA. WARNNING: Make sure to install these dpkg packages in a throw-away environment. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Eoan Ermine test rebuilds
The first test rebuild of Eoan Ermine was started on June 16 2019 for all architectures, all components. Results (please also look at the superseded builds) can be found at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190614-eoan.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. Additional build failures for packages in eoan-proposed (not yet in eoan) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild using GCC 9.1, which will become the default compiler for the 19.10 release. Results at https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190614-gcc9-eoan.html Packages to set GCC 9 as the default GCC can be found in the ubuntu-toolchain-r/volatile PPA. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Test of Eoan 06/19 ISO
HP p7-1010, BIOS, AMD64/ATI6150 graphics, 4GB RAM Deleted one existing partition, installed in it, did some testing, performed well. At first boot, showed error: Whisker menu disappeared, I sent automatic (apport?) report. For QA report, sent a Passed. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Disco Dingo test rebuild
The second test rebuild of Disco Dingo was started on April 04 2019 for all architectures, just the main component. For technical reasons we were not able to start that rebuild earlier, and a rebuild for the universe component wouldn't finish before the 19.04 release. The usual comment about increasing build failures compared to the previous release cannot be proven this time, however a first look at the build failures in main suggests that disco uploads for the kernel, glibc, glib2.0 and vala were made without checking for the impact of build failures. Results (please also look at the superseded builds) can be found at http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-disco-disco.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. Bug reports for all build failures are filed. Additional build failures for packages in disco-proposed (not yet in disco) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Disco ISO of 0304 test
Downloaded 0304 ISO, wrote to USB, tested on HP p7-1010, AMD quad core, 4GB RAM, Radeon graphics. Ran Live as Test Before Installing, started installation from icon, process hung at third page (Download updates while installing). -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Disco Dingo test rebuilds
The first test rebuild of Disco Dingo was started on December 21 2018 for all architectures, all components. The number of build time failures unfortunately is again high, even higher than for the last Cosmic Cuttlefish test rebuild. Results (please also look at the superseded builds) can be found at http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181220-disco.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. Additional build failures for packages in disco-proposed (not yet in disco) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. There is also a test rebuild using an early version of GCC 9, which will become the default compiler for the 19.10 release. Results at http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181220-gcc9-disco.html Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Cosmic Cuttlefish test rebuilds
The first test rebuild of Cosmic Cuttlefish was started on September 11 2018 for all architectures, all components (main component and seeded packages finished, unseeded packages still building). The number of build time failures unfortunately is again high. The test rebuild was done using the openjdk-11 packages from the openjdk-r/ppa PPA (cosmic still has OpenJDK-10, instead of the OpenJDK-11 packages used for the rebuild. Results (please also look at the superseded builds) can be found at http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180911-cosmic.html The report uses some additional color coding, marking packages different which always failed to build, or where the build failure is no regression compared to bionic. Additional build failures for packages in bionic-proposed (not yet in bionic) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Test of latest Xubuntu Core ISO
Installation went smoothly as usual. Added benefit: Dropbox icon does appear, not blocked as in earlier versions. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Bionic Beaver test rebuilds
The second test rebuild of Bionic Beaver was started on April 08 2018 for all architectures, all components (main component and seeded packages finished, unseeded packages still building). The number of build time failures unfortunately is still high. For arm64 and armhf the gcc-7 packages are based on the Linaro 7-2018.03 snapshot. The test rebuild was done using the java-common packages from the bionic-proposed pocket, already pointing to OpenJDK 10 (packaged as openjkd-11). Results (please also look at the superseded builds) can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html Additional build failures for packages in bionic-proposed (not yet in bionic) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using GCC 8 as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-gcc8-bionic.html The GCC 8 test rebuild uses the gcc-defaults packages from the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile We will make GCC 8 the default compiler for the 18.10 release, so please start looking at those build failures as well. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Test of Xubuntu Core 03 April build
I did a Mandatory test (Install to whole disk) on a 2009 Compaq (AMD Athlon 7550 CPU, GeForce 8400 graphics card) and reported it, but I don't see the report listed. The installation went perfectly, and the best part is that the current nouveau driver supports my preferred Compiz with Animations, Sphere, and all. No more need for Nvidia proprietary drivers! Emery -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Test of 20 March Xubuntu Core 18.04 ISO
Tested the 20 March ISO of Xubuntu Core Computer: 2009-era Compaq, AMD CPU, BIOS, 3GB RAM Nvidia GeForce 6400 graphics Opened to Try without installing page Checked that existing installation (Xubuntu Core from 09 March ISO) was mountable Chose Install from Icon Chose Download Updates while installing Chose "Something else" option, set up root and swap partitions Noted that the usual "Warning: here's what it will look like when you continue" (or words to that effect, showing the new partition table) did not appear, it just went ahead and did it correctly Installation went faster than ever: 23minutes start to end, despite slow DSL Currently running well, will report if anything crashes -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
1000 New Year's pledges for 2018 (first Bionic Beaver test rebuilds)
The first test rebuild of Bionic Beaver was started on December 21 2017 for all architectures, all components (main component and seeded packages finished, unseeded packages still building). The number of build time failures unfortunately is at an all time high around a four digit number. Time for some New Year's pledges! For arm64 and armhf the gcc-7 packages are based on the Linaro 7-2017.11 snapshot. Results (please also look at the superseded builds) can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20171220-bionic.html Additional build failures for packages in bionic-proposed (not yet in bionic) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using GCC 8 as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20171220-gcc8-bionic.html The GCC 8 test rebuild uses gcc-defaults and gcc-8 packages from the PPAs https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile It is NOT planned to make GCC 8 the default compiler for bionic beaver, but adding ti as a non-default compiler is still being evaluated. Yet another test rebuild using binutils trunk can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20171220-binutils-bionic.html The binutils test rebuild uses binutils from the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/binutils It is planned to upload binutils trunk to bionic in late January. Happy New Year, Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Ubuntu Artful Aardvark test rebuild
The second test rebuild of Artful Aardvark was started on September 22 for all architectures, all components (main component and seeded packages finished, unseeded packages still building). For arm64 and armhf the gcc-6 and gcc-7 packages are based on the Linaro 6-2017.09 snapshots. Results (please also look at the superseded builds) can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170922-artful.html The test rebuild uses the release pocket only, without packages from the proposed pocket. Additional build failures for packages in artful-proposed (not yet in artful) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Information about transitioning to GCC 7 can be found at: * https://gcc.gnu.org/gcc-7/porting_to.html * https://wiki.debian.org/GCC7 * Please forward patches for GCC 7 build failures to the bug reports already filed in Debian (see the above wiki page for the bug list). Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Ubuntu Artful Aardvark test rebuilds (and upcoming GCC 7 transition)
The first test rebuild of Artful Aardvark was started on July 6 for all architectures, all components (main component and seeded packages finished, unseeded packages still building). For arm64 and armhf the gcc-6 packages are based on the Linaro 6-2017.06 snapshot. Results (please also look at the superseded builds) can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170706-artful.html The test rebuild uses binutils, gcc-6, gcc-7 and linux packages currently still in the proposed release pocket, which can also be found separately in the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa Additional build failures for packages in artful-proposed (not yet in artful) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using GCC 7 as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170706-gcc7-artful.html For arm64 and armhf the gcc-7 packages are based on the Linaro 7-2017.06 snapshot. The test rebuild uses gcc-defaults, binutils, gcc-6, gcc-7 and linux packages currently still in the proposed release pocket, which can also be found separately in the PPA https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/test We are planning the transition to GCC 7 for late July / August. Please help fixing the build issues using the update GCC. Information about transitioning to GCC 7 can be found at: * https://gcc.gnu.org/gcc-7/porting_to.html * https://wiki.debian.org/GCC7 * Please forward patches for GCC 7 build failures to the bug reports already filed in Debian (see the above wiki page for the bug list). Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Ubuntu Zesty Zapus test rebuilds (all components, all architectures, GCC 7)
The second test rebuild of Zesty Zapus was started on March 22 for all architectures, all components (main component and seeded packages finished, unseeded packages still building). For arm64 and armhf the gcc-6 packages are based on the Linaro 6-2017.03 snapshot. Results (please also look at the superseded builds) can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html Additional build failures for packages in zesty-proposed (not yet in zesty) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using a snapshot of GCC 7 (not yet released) as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-gcc7-zesty.html GCC 7 is not yet released and will not be used as the default compiler for the 17.04 release. GCC 7 packages can be found in the ubuntu-toolchain-r/test PPA. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Ubuntu Zesty Zapus test rebuilds (all components, all architectures, GCC 7)
The first test rebuild of Zesty Zapus was started on December 02 for all architectures, all components (main component and seeded packages finished, unseeded packages still building). For arm64 and armhf the gcc-6 packages are based on the Linaro 6-2016.10 snapshot. Results (please also look at the superseded builds) can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20161202-zesty.html Additional build failures for packages in zesty-proposed (not yet in zesty) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using a snapshot of GCC 7 (not yet released) as the default can be found at http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20161202-gcc7-zesty.html GCC 7 is not yet released and will not be used as the default compiler for the 17.04 release. GCC 7 packages can be found in the ubuntu-toolchain-r/test PPA. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Second Ubuntu Yakkety Yak test rebuilds (all components, all architectures, Linaro-GCC)
Responding for ubuntu-server packages...
On 22.09.2016 [14:17:23 +0200], Matthias Klose wrote:
> The second test rebuild of Yakkety Yak was started on September 16 for all
> architectures, all components (main component and seeded packages mostly
> finished, unseeded packages still building).
>
> Results (please also look at the superseded builds) can be found at
>
> http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html
cinder, nova, nova-lxd, python-eventlet, python-taskflow should all be
handled by packages in -proposed by the openstack team. Thanks to them!
libewebp and memcached still have undetermined cause on armhf -- need to
find time next week to debug live, I think.
llvm-toolchain-3.6 has a build-fix in debian, but it then still fails to
pass two tests, still investigating.
python-cffi on ppc64el, reproduced, debugging live.
python-docutils should be fixed on the next test rebuild, as it was a
bug in xml-core. This will probably fix a few other build failures with
the same signature ("dh_installxmlcatalogs: Unexpected debhelper version
format").
xen is fixed per Stefan Bader in the -proposed version.
> Additional build failures for packages in yakkety-proposed (not yet in
> yakkety)
> can be found at http://qa.ubuntuwire.com/ftbfs/
I believe juju team will need to look at the juju-core failure and will
ping the lxc folks on that failure.
Thanks,
Nish
--
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd
--
xubuntu-devel mailing list
xubuntu-devel@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Second Ubuntu Yakkety Yak test rebuilds (all components, all architectures, Linaro-GCC)
The second test rebuild of Yakkety Yak was started on September 16 for all architectures, all components (main component and seeded packages mostly finished, unseeded packages still building). Results (please also look at the superseded builds) can be found at http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-yakkety.html Additional build failures for packages in yakkety-proposed (not yet in yakkety) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Another test rebuild using the Linaro-GCC 6 as the default (planning the defaults change around the end of October) can be found at http://qa.ubuntuwire.org/ftbfs/test-rebuild-20160916-linaro-yakkety.html The corresponding compiler can be found in the ubuntu-toolchain-r/test PPA. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Ubuntu Yakkety Yak test rebuilds (all components, all architectures, GCC 6)
The first test rebuild of Yakkety Yak was started on July 01 for all architectures, all components (main component and seeded packages finished, unseeded packages still building). Results (please also look at the superseded builds) can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160701-yakkety.html Another test rebuild using GCC 6 as the default (planning the defaults change around the end of July) can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160705-gcc6-yakkety.html Please start fixing build failures with GCC 6 now. Porting help can be found at https://gcc.gnu.org/gcc-6/porting_to.html Additional build failures for packages in yakkety-proposed (not yet in yakkety) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
How to test on physical machine since the installation ISO is oversized?
Greetings, I recall seeing a request to test Xubuntu 16.04 on physical hardware verses a VM, such as VirtualBox. How is it possible to burn the ISO to physical media? Ah, create a bootable USB stick of course... That will be a suitable work-around while the ISO images are over sized. I am interested to see if [Bug 1447038] "Shutdown/Restart of live session guest does not work in Virtualbox, and VMWare" goes away installing it to a physical machine. Stay tuned... I am thankful, -- Michael Lueck Lueck Data Systems http://www.lueckdatasystems.com/ -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: How to test packages IRC session
On 22/12/15 20:06, floccul...@gmx.co.uk wrote: Following on from the "How to begin testing session on IRC [1] " we ran in November, we are planning to run a session based around packages. We'll be covering things like, amongst others, using the dev ppa's, how to create useful bug reports, exploratory testing, making sure bugs get reported. We'll be attempting to run this on the 31st January. This is just before a slew of calls for testing of packages and the first of the Beta milestones we'll be participating in this cycle (Beta 1). There is a doodle poll at [2] for people to choose their time(s) from. [1] https://lists.ubuntu.com/archives/xubuntu-devel/2015-November/010966.html [2] http://doodle.com/poll/2h6dfni5gybedvf6 All things being equal - we will be running this session at 16:00 UTC on Sunday 31st January. If you want to come along, but IRC is new to you then there is a webchat tab on our tracker [1] Please try and find the time to check out the contributor docs (chapter 3 - 5) [2] See you there [1] http://tracker.xubuntu.org/#tab-irc [2] http://docs.xubuntu.org/contributors/ -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: How to test packages IRC session
On 22/12/15 20:06, floccul...@gmx.co.uk wrote: Following on from the "How to begin testing session on IRC [1] " we ran in November, we are planning to run a session based around packages. We'll be covering things like, amongst others, using the dev ppa's, how to create useful bug reports, exploratory testing, making sure bugs get reported. We'll be attempting to run this on the 31st January. This is just before a slew of calls for testing of packages and the first of the Beta milestones we'll be participating in this cycle (Beta 1). There is a doodle poll at [2] for people to choose their time(s) from. [1] https://lists.ubuntu.com/archives/xubuntu-devel/2015-November/010966.html [2] http://doodle.com/poll/2h6dfni5gybedvf6 bumping this post-xmas break -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
How to test packages IRC session
Following on from the "How to begin testing session on IRC [1] " we ran in November, we are planning to run a session based around packages. We'll be covering things like, amongst others, using the dev ppa's, how to create useful bug reports, exploratory testing, making sure bugs get reported. We'll be attempting to run this on the 31st January. This is just before a slew of calls for testing of packages and the first of the Beta milestones we'll be participating in this cycle (Beta 1). There is a doodle poll at [2] for people to choose their time(s) from. [1] https://lists.ubuntu.com/archives/xubuntu-devel/2015-November/010966.html [2] http://doodle.com/poll/2h6dfni5gybedvf6 -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: First Wily Werewolf test rebuild
On 02.10.2015 17:12, Matthias Klose wrote: A first test rebuild of Wily Werewolf was started on Oct 01 for all architectures. It is finished for the main component on i386 and amd64. Results can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20151001/ Additional build failures for packages in wily-proposed (not yet in wily) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. the test rebuilds now finished for the amd64, i386 and armhf architectures. Compared to previous releases we still have more build failures compared to previous releases, so pretty please have a look at these build failures and fix these. Relevant URLs are: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html http://qa.ubuntuwire.com/ftbfs/ please also have a look at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html when you uploaded a package you would expect to be in the release pocket but which is still is stuck in wily-proposed. Thanks, Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
First Wily Werewolf test rebuild
A first test rebuild of Wily Werewolf was started on Oct 01 for all architectures. It is finished for the main component on i386 and amd64. Results can be found at http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20151001-wily.html The archive for the test rebuild is https://launchpad.net/ubuntu/+archive/test-rebuild-20151001/ Additional build failures for packages in wily-proposed (not yet in wily) can be found at http://qa.ubuntuwire.com/ftbfs/ Please help fixing the build failures. Matthias -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Late breaking package test ...
I've just added a test for MenuLibre. Can we get eyes on that please and results on the tracker http://packages.qa.ubuntu.com/qatracker/milestones/306/builds/55995/testcases/1638/results Thanks everyone Elfy -- Ubuntu Forum Council Member Xubuntu QA Lead -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Precise milestone test
If anyone can get chance to test these - that would be good. Sorry for the late call - I got caught on the hop ... http://iso.qa.ubuntu.com/qatracker/milestones/311/builds Thanks Elfy -- Ubuntu Forum Council Member Xubuntu QA Lead -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Precise milestone test
Elfy, Done and all passed this morning. Just some minor issues as noted in the QA site. Folks, Please try (at least) the LiveCD test. If you have at least 20GB free space, * Backup all salient data from the current Xubuntu partition or whatever it is (call it P) to a safe place. * Boot with the Live CD or thumb drive (L). * Use `gparted` to shrink P such that 20GB is available for a new Xubuntu partition (12.04.4). * Follow the script and test the along side of installation of 12.04.4. Both Linux partitions (P and 12.04.4) will share the same swap space. * Report results at QA. * Again, boot with L. * Use `gparted` to remove the previous 12.04.4 partition (or wait and do this during manual partitioning). * Follow the script and test the something else [manual partitioning] installation. Again, both Linux partitions will share the same swap space. * Report results at QA. * Again, boot with L. * Use `gparted` to (a) remove the last 12.04.4 partition installed and (b) expand P back to its original size. Richard -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Precise milestone test
Second time - hopefully, it will go in the right place this time (guessing). Elfy, Done and all passed this morning. Just some minor issues as noted in the QA site. Folks, Please try (at least) the LiveCD test. If you have at least 20GB free space, * Backup all salient data from the current Xubuntu partition or whatever it is (call it P) to a safe place. * Boot with the Live CD or thumb drive (L). * Use `gparted` to shrink P such that 20GB is available for a new Xubuntu partition (12.04.4). * Follow the script and test the along side of installation of 12.04.4. Both Linux partitions (P and 12.04.4) will share the same swap space. * Report results at QA. * Again, boot with L. * Use `gparted` to remove the previous 12.04.4 partition (or wait and do this during manual partitioning). * Follow the script and test the something else [manual partitioning] installation. Again, both Linux partitions will share the same swap space. * Report results at QA. * Again, boot with L. * Use `gparted` to (a) remove the last 12.04.4 partition installed and (b) expand P back to its original size. Richard -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
XMir test results for Xubuntu 13.10
Hello, Just completed testing XMir/Mir on two machines with 32-bit ISO image 0.0.9r970. Both test used default graphics drivers. No proprietary binaries used. Machine One: Old HP Pavillion with Intel 1.5 GHz Pentium4 and 768MB memory. Graphics card is GeForce FX 5200 with 128MB vid memory. Intial bootup with DVD presented blank screen with blinking cursor in upper left of screen for about 20secs, then Plymouth screen took over for about a minute or two (expected with old machine with less than 1GB of mem). Screen then blanked for several seconds until desktop appeared with a xfce4-terminal present. Text error message in terminal read : Mesa 9.1.6 implementation error: Incomplete OpenGL ES 2.0 support. Please report at bugs.freedesktop.org unity-system-compositor: ../../../../../src/mesa/main/context.c:1551: _mesa_make_current: Assertion `newCtx-Version 0' failed. Aborted (core dumped) Test successful since failover to Xorg completed without problems. Machine Two: Less older Dell Inspiron 570 with dual core AMD Athlon II X2 245 Processor and 4GB memory. Graphics is on-board ATI Radeon HD 4200 w/ 256MB mem. Bootup with DVD went to Plymouth screen after a few seconds and brought up desktop shortly thereafter. Confirmed that unity-system- compsitor programs were loaded with pgrep command. Notes: Mouse movement was sluggish, though still usuable. Tweaking mouse acceleration didn't really help as it then became too easy to overshoot click target. Windows appeared/minimized/maximized very snappily. GUI function response inside of application (selecting menu options, buttons pushed, checkbox selection, dropdown lists, etc.) was also snappy. Even though moving windows around screen was slow because of the sluggish mouse, the movement produced no perceptible tearing. Text input in Abiword, Mousepad, Gnumeric, Firefox with a webform display showed no sign of sluggishness or delay between keystroke and display on screen. Text selection in those apps for cut-n-paste was fast and had no problems. No perceptible lag, screen artifacts, or discoloration when playing video in Parole, either in window or full screen mode. Transition between modes was also seamless. Graphics programs like Gimp and gthumb had no issues with displaying or editing images save for a mouse pointer issue described below. In applications that change the mouse pointer from an arrow to, say, a zoom magnifying glass (like Firefox does when viewing a large image), the pointer has a small box surrounding it and inside the pointer looks like it has mouse trails turned on. Same thing happens in Gnumeric when it changes the pointer to a +. Overall, because the slow mouse movement is a significant performance regression, the test must result in a failed status. Mir is almost there, but not quite. -- sktsee -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
XMir on Xubuntu Install Test with Intel GMA 3650 graphics
Just down-loaded the ISO (08/13/13 Version: 0.0.9r970) from http://vanir.unit193.tk/mir/. I used it to install on my rig described below. Then, I performed an apt-get update and dist-upgrade to make sure that I was testing an up-to-date system. Summary: (1) While the compositor did try to come up, it gave up and returned an exit code of 1 according to the lightdm.log. The unity-system-compositor.log contained the following: ERROR: /build/buildd/mir-0.0.9+13.10.20130813/src/server/graphics/gbm/gbm_display_helpers.cpp(305): Throw in function void mir::graphics::gbm::helpers::GBMHelper::setup(const mir::graphics::gbm::helpers::DRMHelper) Dynamic exception type: boost::exception_detail::clone_implboost::exception_detail::error_info_injectorstd::runtime_error std::exception::what: Failed to create GBM device (2) Lightdm handled the exit code by starting an X session as a replacement. The resulting Lightdm on X on Linux kernel 3.11.0-2 is quite stable. Queries or further testing? Richard Motherboard: Intel D2550MUD2 (for better and worse!) * Mini-ITX * Dual-core Intel Atom D2550 CPU * Intel NM10 Express chipset * Intel GMA 3650 graphics (Cedar View) http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-d2550mud2.html?wapkw=d2550mud2 http://www.intel.com/p/en_US/support/category/dsktpboards/db-d2550mud2/doc_guide?format-type=Technical+Documents http://en.wikipedia.org/wiki/Intel_GMA -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
URL xMir test results
http://pad.ubuntu.com/ep/pad/view/A1WJwaAxZx/latest -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
Thanks so much for the responses, everyone. I guess, I missed that part on the announcements. I still think we should put something about that in the requirements list, though. Something under Minimum system requirements? - Joan On Mon, Jul 29, 2013 at 10:43 AM, Bruno Benitez gridc...@gmail.com wrote: 2013/7/29 David Segura M david...@gmail.com HI There is no need to over react, they can still work using 12.04, but there is also a way to do it with 13.04 with a little of work. An important number of old Thinkpads use a Pentim M processor (as in the case of Joan) so the are afected by this problem which is the following: A number of older Pentium Mhttp://en.wikipedia.org/wiki/List_of_Intel_Pentium_M_microprocessorsprocessors produced around 2003-4 (the ones with 400 MHz front side bus) do not display the PAE flag, and hence a standard installation fails. However, these processors are in fact able to run the latest (and PAE-demanding) kernels if only the installation process is modified a little. As stated in https://help.ubuntu.com/community/PAE, also there are the options you can choose and the procedure to follow, of course in step 6 you can choose and put xlubuntu-desktop instead. well put :) -- Bruno.- -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel -- Joan Advincula Mozilla Rep, https://reps.mozilla.org/u/jadvincula/ @iamMJae http://twitter.com/iamMJae | http://jauntyskipper.wordpress.com -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
By the way, I think we also need to clarify the CPU type and whatnot. (There are still lots of things about CPU's that I don't understand.) I tried installing 13.04 on an old IBM ThinkPad and it wouldn't install because the CPU is missing something, apparently. (It runs on and Intel Pentium M 1600 MHz.) Something about pae. I'm still Googling that part though so this might be irrelevant. - Joan On Tue, Jul 23, 2013 at 2:42 PM, PK pliniusmi...@gmail.com wrote: I agree with Ali Linx, that 512 MB RAM should be considered as a workable minimum for Xubuntu. If it gets lower than that, Lubuntu or even mini's like AntiX or Puppy Linux are much more suitable. In my opinion, the minimal system requirements should be aimed at a practical and workable system, not at a theoretical minimum that will, at best, cause an unbearably slow and sluggish system. Underpromise and overdeliver, that's what makes people happy Not the other way round. :-) I have no figures to back my statement, but I do have the experience of seven years of fulltime Linux use on many computers. Regards, Pjotr. 2013/7/23 Jeff Hanson jephhan...@gmail.com Could you have actually opened the System Monitor to see how much ram and how much swap was being used at the time, or did I miss something? I just wouldn't like to assume that it is going over etc based on overall performance, when it's easy to see how much is being used in real time and from what apps. On Wed, Jul 17, 2013 at 12:15 AM, Ali Linx (amjjawad) amjja...@gmail.com wrote: On Wed, Jul 17, 2013 at 8:59 AM, Micah Gersten mic...@ubuntu.comwrote: On 07/16/2013 11:33 PM, Ali Linx (amjjawad) wrote: Hi, *Information:* - Xubuntu 12.04.1.ISO - LiveUSB Created by UNetbootin - Installation on Real Hardware - http://phillw.net/hardware/BnA9pw11 - RAM Used: 242MB - http://i44.tinypic.com/a4ug5s.jpg - Note that: LiveUSB is faster than LiveCD *Test Case:* 1. Machine has two HDD1 and HDD2 2. HDD1 is Samsung 20GB IDE (Lubuntu 13.10 Saucy is installed on the whole HDD). 3. HHD2 is Segate 80GB IDE 4. Booting the machine from the LiveUSB 5. Choosing Try Xubuntu without installation 6. Booted successfully to the Live Desktop 7. http://i44.tinypic.com/2hf5tgj.jpg 8. The Live Desktop was slow and I had to wait few seconds until Right Click Menu shows up. 9. Ran GParted to turn SWAP OFF. 10. Once SWAP is OFF, the machine became VERY SLOW. If I press CAPS Lock, the LED on the Keyboards needs few mins to be ON. 11. Obviously, because Physical RAM was already being used (FULLY) - http://i44.tinypic.com/2hf5tgj.jpg - then once SWAP is OFF, definitely the whole machine will stop responding and this is very easy to re-produce (I'm expert to make old machine not usable and not responding). 12. Clicked on Install Xubuntu from the Desktop 13. I waited for 30 mins and the machine is totally not responding and the mouse pointer is stuck on the circle icon (when the system is processing something, the pointer turns to be a circle - I'm sure you know what I mean). 14. I had to reboot the machine. 15. Repeated the same above steps - same result 16. Even though the Live Desktop did not crash after 30mins of waiting, the whole system/machine is not usable and not responding so whether it crashes or not, same - you can not do anything and you must reboot. *Summary:* Having all the above said, long story short, there is *NO WAY* to 'Try' Xubuntu on 256MB of RAM nor 'Installing' it with 256MB of RAM. Again, see this: http://i44.tinypic.com/2hf5tgj.jpg *Suggestion:* I think by far, it is very much safe to say that the *Minimum RAM*required to Try Xubuntu and/or Install it is 512MB AT LEAST. *Please Note:* You need to understand that having a pre-exist SWAP Partition is NOT the default/standard case for all users. Users may have only one HDD. User may have not installer another Linux System on a different or same HDD so they do have SWAP. Also, please note that it is NOT advisable to ask from a new user to create a SWAP Partition just to install Xubuntu on LESS than 512MB RAM. This is not helpful at all, IMHO. Having that said, in order to do a real test with a worse case scenario, you need to follow the steps I have done to get the same results (SWAP OFF). *By the way ... if zRAM was enabled by default, I'm sure the results would be different - just saying *:) *What Next?* On the same machine, I am going to increase the RAM used by system by entering BIOS and: http://i44.tinypic.com/a4ug5s.jpg I will set it to 64MB so the RAM that will be used by the system will be 432MB RAM. I know what you are thinking. There is 16MB any Linux OS I have tried on that machine can not read/detect that is why the usable RAM by the system is 432MB not 448MB. Yes, I will turn SWAP OFF as well. Ok, I have tried
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
Joan, kernel for non-PAE microprocessors was dropped since 12.10, last ISO with non-PAE kernel support was 12.04, see the release notes http://xubuntu.org/news/12-04-release/ :) 2013/7/29 Joan Advincula mj.advinc...@gmail.com By the way, I think we also need to clarify the CPU type and whatnot. (There are still lots of things about CPU's that I don't understand.) I tried installing 13.04 on an old IBM ThinkPad and it wouldn't install because the CPU is missing something, apparently. (It runs on and Intel Pentium M 1600 MHz.) Something about pae. I'm still Googling that part though so this might be irrelevant. - Joan On Tue, Jul 23, 2013 at 2:42 PM, PK pliniusmi...@gmail.com wrote: I agree with Ali Linx, that 512 MB RAM should be considered as a workable minimum for Xubuntu. If it gets lower than that, Lubuntu or even mini's like AntiX or Puppy Linux are much more suitable. In my opinion, the minimal system requirements should be aimed at a practical and workable system, not at a theoretical minimum that will, at best, cause an unbearably slow and sluggish system. Underpromise and overdeliver, that's what makes people happy Not the other way round. :-) I have no figures to back my statement, but I do have the experience of seven years of fulltime Linux use on many computers. Regards, Pjotr. 2013/7/23 Jeff Hanson jephhan...@gmail.com Could you have actually opened the System Monitor to see how much ram and how much swap was being used at the time, or did I miss something? I just wouldn't like to assume that it is going over etc based on overall performance, when it's easy to see how much is being used in real time and from what apps. On Wed, Jul 17, 2013 at 12:15 AM, Ali Linx (amjjawad) amjja...@gmail.com wrote: On Wed, Jul 17, 2013 at 8:59 AM, Micah Gersten mic...@ubuntu.comwrote: On 07/16/2013 11:33 PM, Ali Linx (amjjawad) wrote: Hi, *Information:* - Xubuntu 12.04.1.ISO - LiveUSB Created by UNetbootin - Installation on Real Hardware - http://phillw.net/hardware/BnA9pw11 - RAM Used: 242MB - http://i44.tinypic.com/a4ug5s.jpg - Note that: LiveUSB is faster than LiveCD *Test Case:* 1. Machine has two HDD1 and HDD2 2. HDD1 is Samsung 20GB IDE (Lubuntu 13.10 Saucy is installed on the whole HDD). 3. HHD2 is Segate 80GB IDE 4. Booting the machine from the LiveUSB 5. Choosing Try Xubuntu without installation 6. Booted successfully to the Live Desktop 7. http://i44.tinypic.com/2hf5tgj.jpg 8. The Live Desktop was slow and I had to wait few seconds until Right Click Menu shows up. 9. Ran GParted to turn SWAP OFF. 10. Once SWAP is OFF, the machine became VERY SLOW. If I press CAPS Lock, the LED on the Keyboards needs few mins to be ON. 11. Obviously, because Physical RAM was already being used (FULLY) - http://i44.tinypic.com/2hf5tgj.jpg - then once SWAP is OFF, definitely the whole machine will stop responding and this is very easy to re-produce (I'm expert to make old machine not usable and not responding). 12. Clicked on Install Xubuntu from the Desktop 13. I waited for 30 mins and the machine is totally not responding and the mouse pointer is stuck on the circle icon (when the system is processing something, the pointer turns to be a circle - I'm sure you know what I mean). 14. I had to reboot the machine. 15. Repeated the same above steps - same result 16. Even though the Live Desktop did not crash after 30mins of waiting, the whole system/machine is not usable and not responding so whether it crashes or not, same - you can not do anything and you must reboot. *Summary:* Having all the above said, long story short, there is *NO WAY* to 'Try' Xubuntu on 256MB of RAM nor 'Installing' it with 256MB of RAM. Again, see this: http://i44.tinypic.com/2hf5tgj.jpg *Suggestion:* I think by far, it is very much safe to say that the *Minimum RAM*required to Try Xubuntu and/or Install it is 512MB AT LEAST. *Please Note:* You need to understand that having a pre-exist SWAP Partition is NOT the default/standard case for all users. Users may have only one HDD. User may have not installer another Linux System on a different or same HDD so they do have SWAP. Also, please note that it is NOT advisable to ask from a new user to create a SWAP Partition just to install Xubuntu on LESS than 512MB RAM. This is not helpful at all, IMHO. Having that said, in order to do a real test with a worse case scenario, you need to follow the steps I have done to get the same results (SWAP OFF). *By the way ... if zRAM was enabled by default, I'm sure the results would be different - just saying *:) *What Next?* On the same machine, I am going to increase the RAM used by system by entering BIOS and: http://i44.tinypic.com/a4ug5s.jpg I will set it to 64MB so the RAM that will be used by the system
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
so dear linux-team, does it means: all old notebooks and computer are to die ? there must be a way to keep old maschine alife ! looking forward to a how to , peter Am 29.07.2013 14:19, schrieb Bruno Benitez: Joan, kernel for non-PAE microprocessors was dropped since 12.10, last ISO with non-PAE kernel support was 12.04, see the release notes http://xubuntu.org/news/12-04-release/ :) 2013/7/29 Joan Advincula mj.advinc...@gmail.com mailto:mj.advinc...@gmail.com By the way, I think we also need to clarify the CPU type and whatnot. (There are still lots of things about CPU's that I don't understand.) I tried installing 13.04 on an old IBM ThinkPad and it wouldn't install because the CPU is missing something, apparently. (It runs on and Intel Pentium M 1600 MHz.) Something about pae. I'm still Googling that part though so this might be irrelevant. - Joan -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
Peter, keep in mind that Xubuntu its NOT the linux-team. Non PAE kernel support its still possible, but Xubuntu will NOT support it, there are however many other distros who are aimed toward older computers that WILL NOT drop old computers support. However Xubuntu its not one of those distros. We focus on giving a modern and stable desktop. 2013/7/29 peter a.gil...@mo-po.de so dear linux-team, does it means: all old notebooks and computer are to die ? there must be a way to keep old maschine alife ! looking forward to a how to , peter Am 29.07.2013 14:19, schrieb Bruno Benitez: Joan, kernel for non-PAE microprocessors was dropped since 12.10, last ISO with non-PAE kernel support was 12.04, see the release notes http://xubuntu.org/news/12-04-release/ :) 2013/7/29 Joan Advincula mj.advinc...@gmail.com By the way, I think we also need to clarify the CPU type and whatnot. (There are still lots of things about CPU's that I don't understand.) I tried installing 13.04 on an old IBM ThinkPad and it wouldn't install because the CPU is missing something, apparently. (It runs on and Intel Pentium M 1600 MHz.) Something about pae. I'm still Googling that part though so this might be irrelevant. - Joan -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel -- Bruno.- -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
HI There is no need to over react, they can still work using 12.04, but there is also a way to do it with 13.04 with a little of work. An important number of old Thinkpads use a Pentim M processor (as in the case of Joan) so the are afected by this problem which is the following: A number of older Pentium M http://en.wikipedia.org/wiki/List_of_Intel_Pentium_M_microprocessors processors produced around 2003-4 (the ones with 400 MHz front side bus) do not display the PAE flag, and hence a standard installation fails. However, these processors are in fact able to run the latest (and PAE-demanding) kernels if only the installation process is modified a little. As stated in https://help.ubuntu.com/community/PAE, also there are the options you can choose and the procedure to follow, of course in step 6 you can choose and put xlubuntu-desktop instead. El 29/07/13 07:33, peter escribió: so dear linux-team, does it means: all old notebooks and computer are to die ? there must be a way to keep old maschine alife ! looking forward to a how to , peter Am 29.07.2013 14:19, schrieb Bruno Benitez: Joan, kernel for non-PAE microprocessors was dropped since 12.10, last ISO with non-PAE kernel support was 12.04, see the release notes http://xubuntu.org/news/12-04-release/ :) 2013/7/29 Joan Advincula mj.advinc...@gmail.com mailto:mj.advinc...@gmail.com By the way, I think we also need to clarify the CPU type and whatnot. (There are still lots of things about CPU's that I don't understand.) I tried installing 13.04 on an old IBM ThinkPad and it wouldn't install because the CPU is missing something, apparently. (It runs on and Intel Pentium M 1600 MHz.) Something about pae. I'm still Googling that part though so this might be irrelevant. - Joan -- David Segura M -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Manual Test Case Questions (time-admin)
I've started working on the manual testcase for the time administration tool (Bug #1184676) and have a couple of questions for the devs and QA folks. The first problem occurs when you try to switch the configuration from 'Manual' to 'Keep synchronized with Internet servers'. Sync requires the ntp deamon, which is not installed by default, so time-admin gives the option to install it. Problem is, it doesn't work. If synaptic is not installed, time-admin says it doesn't have the required apps to do the install. If synaptic is installed, time-admin either hangs or crashes. So, knowing this up front, my question is how to write the testcase. Do I say there's a known bug so make sure you install ntp manually first? Or write it up like it's supposed to work and just let people keep finding out it doesn't until it's fixed? The second issue is that the help file is outdated. It refers to a version of time-admin that pre-dates Precise and includes instructions on how to choose a time server - an option that is no longer offered. Same question here: what should I say about that in the testcase? Is this utility still being actively developed? According to the changelog, it looks like that last updates happened around Precise. Thanks, Jack -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
I don't exactly have solid figures to give but I've been using Xubuntu 12.04 on an Asus EeePC 701 which only has 512 Mb of RAM so that's a safe number. It's won't be a theoretical minimum. Of course, I had to use the alternative installer. - Joan On Tue, Jul 23, 2013 at 2:42 PM, PK pliniusmi...@gmail.com wrote: I agree with Ali Linx, that 512 MB RAM should be considered as a workable minimum for Xubuntu. If it gets lower than that, Lubuntu or even mini's like AntiX or Puppy Linux are much more suitable. In my opinion, the minimal system requirements should be aimed at a practical and workable system, not at a theoretical minimum that will, at best, cause an unbearably slow and sluggish system. Underpromise and overdeliver, that's what makes people happy Not the other way round. :-) I have no figures to back my statement, but I do have the experience of seven years of fulltime Linux use on many computers. Regards, Pjotr. 2013/7/23 Jeff Hanson jephhan...@gmail.com Could you have actually opened the System Monitor to see how much ram and how much swap was being used at the time, or did I miss something? I just wouldn't like to assume that it is going over etc based on overall performance, when it's easy to see how much is being used in real time and from what apps. On Wed, Jul 17, 2013 at 12:15 AM, Ali Linx (amjjawad) amjja...@gmail.com wrote: On Wed, Jul 17, 2013 at 8:59 AM, Micah Gersten mic...@ubuntu.comwrote: On 07/16/2013 11:33 PM, Ali Linx (amjjawad) wrote: Hi, *Information:* - Xubuntu 12.04.1.ISO - LiveUSB Created by UNetbootin - Installation on Real Hardware - http://phillw.net/hardware/BnA9pw11 - RAM Used: 242MB - http://i44.tinypic.com/a4ug5s.jpg - Note that: LiveUSB is faster than LiveCD *Test Case:* 1. Machine has two HDD1 and HDD2 2. HDD1 is Samsung 20GB IDE (Lubuntu 13.10 Saucy is installed on the whole HDD). 3. HHD2 is Segate 80GB IDE 4. Booting the machine from the LiveUSB 5. Choosing Try Xubuntu without installation 6. Booted successfully to the Live Desktop 7. http://i44.tinypic.com/2hf5tgj.jpg 8. The Live Desktop was slow and I had to wait few seconds until Right Click Menu shows up. 9. Ran GParted to turn SWAP OFF. 10. Once SWAP is OFF, the machine became VERY SLOW. If I press CAPS Lock, the LED on the Keyboards needs few mins to be ON. 11. Obviously, because Physical RAM was already being used (FULLY) - http://i44.tinypic.com/2hf5tgj.jpg - then once SWAP is OFF, definitely the whole machine will stop responding and this is very easy to re-produce (I'm expert to make old machine not usable and not responding). 12. Clicked on Install Xubuntu from the Desktop 13. I waited for 30 mins and the machine is totally not responding and the mouse pointer is stuck on the circle icon (when the system is processing something, the pointer turns to be a circle - I'm sure you know what I mean). 14. I had to reboot the machine. 15. Repeated the same above steps - same result 16. Even though the Live Desktop did not crash after 30mins of waiting, the whole system/machine is not usable and not responding so whether it crashes or not, same - you can not do anything and you must reboot. *Summary:* Having all the above said, long story short, there is *NO WAY* to 'Try' Xubuntu on 256MB of RAM nor 'Installing' it with 256MB of RAM. Again, see this: http://i44.tinypic.com/2hf5tgj.jpg *Suggestion:* I think by far, it is very much safe to say that the *Minimum RAM*required to Try Xubuntu and/or Install it is 512MB AT LEAST. *Please Note:* You need to understand that having a pre-exist SWAP Partition is NOT the default/standard case for all users. Users may have only one HDD. User may have not installer another Linux System on a different or same HDD so they do have SWAP. Also, please note that it is NOT advisable to ask from a new user to create a SWAP Partition just to install Xubuntu on LESS than 512MB RAM. This is not helpful at all, IMHO. Having that said, in order to do a real test with a worse case scenario, you need to follow the steps I have done to get the same results (SWAP OFF). *By the way ... if zRAM was enabled by default, I'm sure the results would be different - just saying *:) *What Next?* On the same machine, I am going to increase the RAM used by system by entering BIOS and: http://i44.tinypic.com/a4ug5s.jpg I will set it to 64MB so the RAM that will be used by the system will be 432MB RAM. I know what you are thinking. There is 16MB any Linux OS I have tried on that machine can not read/detect that is why the usable RAM by the system is 432MB not 448MB. Yes, I will turn SWAP OFF as well. Ok, I have tried that and I did not work. I had to set the RAM to 464MB so that I can install Xubuntu 12.04 from the LiveUSB while I'm on the Live Desktop (Try Xubuntu
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
Could you have actually opened the System Monitor to see how much ram and how much swap was being used at the time, or did I miss something? I just wouldn't like to assume that it is going over etc based on overall performance, when it's easy to see how much is being used in real time and from what apps. On Wed, Jul 17, 2013 at 12:15 AM, Ali Linx (amjjawad) amjja...@gmail.comwrote: On Wed, Jul 17, 2013 at 8:59 AM, Micah Gersten mic...@ubuntu.com wrote: On 07/16/2013 11:33 PM, Ali Linx (amjjawad) wrote: Hi, *Information:* - Xubuntu 12.04.1.ISO - LiveUSB Created by UNetbootin - Installation on Real Hardware - http://phillw.net/hardware/BnA9pw11 - RAM Used: 242MB - http://i44.tinypic.com/a4ug5s.jpg - Note that: LiveUSB is faster than LiveCD *Test Case:* 1. Machine has two HDD1 and HDD2 2. HDD1 is Samsung 20GB IDE (Lubuntu 13.10 Saucy is installed on the whole HDD). 3. HHD2 is Segate 80GB IDE 4. Booting the machine from the LiveUSB 5. Choosing Try Xubuntu without installation 6. Booted successfully to the Live Desktop 7. http://i44.tinypic.com/2hf5tgj.jpg 8. The Live Desktop was slow and I had to wait few seconds until Right Click Menu shows up. 9. Ran GParted to turn SWAP OFF. 10. Once SWAP is OFF, the machine became VERY SLOW. If I press CAPS Lock, the LED on the Keyboards needs few mins to be ON. 11. Obviously, because Physical RAM was already being used (FULLY) - http://i44.tinypic.com/2hf5tgj.jpg - then once SWAP is OFF, definitely the whole machine will stop responding and this is very easy to re-produce (I'm expert to make old machine not usable and not responding). 12. Clicked on Install Xubuntu from the Desktop 13. I waited for 30 mins and the machine is totally not responding and the mouse pointer is stuck on the circle icon (when the system is processing something, the pointer turns to be a circle - I'm sure you know what I mean). 14. I had to reboot the machine. 15. Repeated the same above steps - same result 16. Even though the Live Desktop did not crash after 30mins of waiting, the whole system/machine is not usable and not responding so whether it crashes or not, same - you can not do anything and you must reboot. *Summary:* Having all the above said, long story short, there is *NO WAY* to 'Try' Xubuntu on 256MB of RAM nor 'Installing' it with 256MB of RAM. Again, see this: http://i44.tinypic.com/2hf5tgj.jpg *Suggestion:* I think by far, it is very much safe to say that the *Minimum RAM*required to Try Xubuntu and/or Install it is 512MB AT LEAST. *Please Note:* You need to understand that having a pre-exist SWAP Partition is NOT the default/standard case for all users. Users may have only one HDD. User may have not installer another Linux System on a different or same HDD so they do have SWAP. Also, please note that it is NOT advisable to ask from a new user to create a SWAP Partition just to install Xubuntu on LESS than 512MB RAM. This is not helpful at all, IMHO. Having that said, in order to do a real test with a worse case scenario, you need to follow the steps I have done to get the same results (SWAP OFF). *By the way ... if zRAM was enabled by default, I'm sure the results would be different - just saying *:) *What Next?* On the same machine, I am going to increase the RAM used by system by entering BIOS and: http://i44.tinypic.com/a4ug5s.jpg I will set it to 64MB so the RAM that will be used by the system will be 432MB RAM. I know what you are thinking. There is 16MB any Linux OS I have tried on that machine can not read/detect that is why the usable RAM by the system is 432MB not 448MB. Yes, I will turn SWAP OFF as well. Ok, I have tried that and I did not work. I had to set the RAM to 464MB so that I can install Xubuntu 12.04 from the LiveUSB while I'm on the Live Desktop (Try Xubuntu without installation Live Desktop). and ... Installation is successful - Time:13mins *After Installation Xubuntu 12.04* This is what I did after the installation: 1. sudo nano /etc/fstab 2. Removed SWAP entry 3. Saved 4. Rebooted 5. sudo apt-get install zram-config 6. http://i40.tinypic.com/n2cqq9.jpg I'm currently upgrading my system: sudo apt-get upgrade sudo apt-get dist-upgrade Now, Xubuntu 12.04 installation has NO Physical SWAP Partition. The SWAP that you see here: http://i40.tinypic.com/n2cqq9.jpg This is from zram-config http://en.wikipedia.org/wiki/ZRam https://launchpad.net/ubuntu/+source/zram-config *End of Test Report 1* Thank you for reading! -- All of us are smarter than any one of us. *Best Regards,* *amjjawad https://wiki.ubuntu.com/amjjawad/* *Start Ubuntuhttps://wiki.ubuntu.com/Lubuntu/CommunicationsTeam/WOWLubuntu/StartUbuntu * *My Own Business http://alilinx.blogspot.com/* I don't think that anyone
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
On 07/16/2013 11:33 PM, Ali Linx (amjjawad) wrote: Hi, *_Information:_* - Xubuntu 12.04.1.ISO - LiveUSB Created by UNetbootin - Installation on Real Hardware - http://phillw.net/hardware/BnA9pw11 - RAM Used: 242MB - http://i44.tinypic.com/a4ug5s.jpg - Note that: LiveUSB is faster than LiveCD *_Test Case:_* 1. Machine has two HDD1 and HDD2 2. HDD1 is Samsung 20GB IDE (Lubuntu 13.10 Saucy is installed on the whole HDD). 3. HHD2 is Segate 80GB IDE 4. Booting the machine from the LiveUSB 5. Choosing Try Xubuntu without installation 6. Booted successfully to the Live Desktop 7. http://i44.tinypic.com/2hf5tgj.jpg 8. The Live Desktop was slow and I had to wait few seconds until Right Click Menu shows up. 9. Ran GParted to turn SWAP OFF. 10. Once SWAP is OFF, the machine became VERY SLOW. If I press CAPS Lock, the LED on the Keyboards needs few mins to be ON. 11. Obviously, because Physical RAM was already being used (FULLY) - http://i44.tinypic.com/2hf5tgj.jpg - then once SWAP is OFF, definitely the whole machine will stop responding and this is very easy to re-produce (I'm expert to make old machine not usable and not responding). 12. Clicked on Install Xubuntu from the Desktop 13. I waited for 30 mins and the machine is totally not responding and the mouse pointer is stuck on the circle icon (when the system is processing something, the pointer turns to be a circle - I'm sure you know what I mean). 14. I had to reboot the machine. 15. Repeated the same above steps - same result 16. Even though the Live Desktop did not crash after 30mins of waiting, the whole system/machine is not usable and not responding so whether it crashes or not, same - you can not do anything and you must reboot. *_Summary:_* Having all the above said, long story short, there is *_NO WAY_* to 'Try' Xubuntu on 256MB of RAM nor 'Installing' it with 256MB of RAM. Again, see this: http://i44.tinypic.com/2hf5tgj.jpg *_Suggestion:_* I think by far, it is very much safe to say that the *_Minimum RAM_* required to Try Xubuntu and/or Install it is 512MB AT LEAST. *_Please Note:_* You need to understand that having a pre-exist SWAP Partition is NOT the default/standard case for all users. Users may have only one HDD. User may have not installer another Linux System on a different or same HDD so they do have SWAP. Also, please note that it is NOT advisable to ask from a new user to create a SWAP Partition just to install Xubuntu on LESS than 512MB RAM. This is not helpful at all, IMHO. Having that said, in order to do a real test with a worse case scenario, you need to follow the steps I have done to get the same results (SWAP OFF). /By the way ... if zRAM was enabled by default, I'm sure the results would be different - just saying /:) *_What Next?_* On the same machine, I am going to increase the RAM used by system by entering BIOS and: http://i44.tinypic.com/a4ug5s.jpg I will set it to 64MB so the RAM that will be used by the system will be 432MB RAM. I know what you are thinking. There is 16MB any Linux OS I have tried on that machine can not read/detect that is why the usable RAM by the system is 432MB not 448MB. Yes, I will turn SWAP OFF as well. Ok, I have tried that and I did not work. I had to set the RAM to 464MB so that I can install Xubuntu 12.04 from the LiveUSB while I'm on the Live Desktop (Try Xubuntu without installation Live Desktop). and ... Installation is successful - Time:13mins *_After Installation Xubuntu 12.04_* This is what I did after the installation: 1. sudo nano /etc/fstab 2. Removed SWAP entry 3. Saved 4. Rebooted 5. sudo apt-get install zram-config 6. http://i40.tinypic.com/n2cqq9.jpg I'm currently upgrading my system: sudo apt-get upgrade sudo apt-get dist-upgrade Now, Xubuntu 12.04 installation has NO Physical SWAP Partition. The SWAP that you see here: http://i40.tinypic.com/n2cqq9.jpg This is from zram-config http://en.wikipedia.org/wiki/ZRam https://launchpad.net/ubuntu/+source/zram-config *End of Test Report 1* Thank you for reading! -- All of us are smarter than any one of us. *Best Regards,* *amjjawad https://wiki.ubuntu.com/amjjawad/* *Start Ubuntu https://wiki.ubuntu.com/Lubuntu/CommunicationsTeam/WOWLubuntu/StartUbuntu* *My Own Business http://alilinx.blogspot.com/* I don't think that anyone says to run Xubuntu with 256MB RAM with no swap partition. Creating a swap partition is a part of the standard install IIRC. Also, this can be a swap file and does not need to be a separate disk (though I don't know if the installer handles this properly or not). Having said that, I don't have an issue saying that the minimum to run Xubuntu is 512MB at this point. Even at 512MB, swap will be needed, but I don't think that's a problem. Micah -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https
Re: [Test Report 1] Minimum System Requirement for Xubuntu 12.04 LTS
On Wed, Jul 17, 2013 at 8:59 AM, Micah Gersten mic...@ubuntu.com wrote: On 07/16/2013 11:33 PM, Ali Linx (amjjawad) wrote: Hi, *Information:* - Xubuntu 12.04.1.ISO - LiveUSB Created by UNetbootin - Installation on Real Hardware - http://phillw.net/hardware/BnA9pw11 - RAM Used: 242MB - http://i44.tinypic.com/a4ug5s.jpg - Note that: LiveUSB is faster than LiveCD *Test Case:* 1. Machine has two HDD1 and HDD2 2. HDD1 is Samsung 20GB IDE (Lubuntu 13.10 Saucy is installed on the whole HDD). 3. HHD2 is Segate 80GB IDE 4. Booting the machine from the LiveUSB 5. Choosing Try Xubuntu without installation 6. Booted successfully to the Live Desktop 7. http://i44.tinypic.com/2hf5tgj.jpg 8. The Live Desktop was slow and I had to wait few seconds until Right Click Menu shows up. 9. Ran GParted to turn SWAP OFF. 10. Once SWAP is OFF, the machine became VERY SLOW. If I press CAPS Lock, the LED on the Keyboards needs few mins to be ON. 11. Obviously, because Physical RAM was already being used (FULLY) - http://i44.tinypic.com/2hf5tgj.jpg - then once SWAP is OFF, definitely the whole machine will stop responding and this is very easy to re-produce (I'm expert to make old machine not usable and not responding). 12. Clicked on Install Xubuntu from the Desktop 13. I waited for 30 mins and the machine is totally not responding and the mouse pointer is stuck on the circle icon (when the system is processing something, the pointer turns to be a circle - I'm sure you know what I mean). 14. I had to reboot the machine. 15. Repeated the same above steps - same result 16. Even though the Live Desktop did not crash after 30mins of waiting, the whole system/machine is not usable and not responding so whether it crashes or not, same - you can not do anything and you must reboot. *Summary:* Having all the above said, long story short, there is *NO WAY* to 'Try' Xubuntu on 256MB of RAM nor 'Installing' it with 256MB of RAM. Again, see this: http://i44.tinypic.com/2hf5tgj.jpg *Suggestion:* I think by far, it is very much safe to say that the *Minimum RAM*required to Try Xubuntu and/or Install it is 512MB AT LEAST. *Please Note:* You need to understand that having a pre-exist SWAP Partition is NOT the default/standard case for all users. Users may have only one HDD. User may have not installer another Linux System on a different or same HDD so they do have SWAP. Also, please note that it is NOT advisable to ask from a new user to create a SWAP Partition just to install Xubuntu on LESS than 512MB RAM. This is not helpful at all, IMHO. Having that said, in order to do a real test with a worse case scenario, you need to follow the steps I have done to get the same results (SWAP OFF). *By the way ... if zRAM was enabled by default, I'm sure the results would be different - just saying *:) *What Next?* On the same machine, I am going to increase the RAM used by system by entering BIOS and: http://i44.tinypic.com/a4ug5s.jpg I will set it to 64MB so the RAM that will be used by the system will be 432MB RAM. I know what you are thinking. There is 16MB any Linux OS I have tried on that machine can not read/detect that is why the usable RAM by the system is 432MB not 448MB. Yes, I will turn SWAP OFF as well. Ok, I have tried that and I did not work. I had to set the RAM to 464MB so that I can install Xubuntu 12.04 from the LiveUSB while I'm on the Live Desktop (Try Xubuntu without installation Live Desktop). and ... Installation is successful - Time:13mins *After Installation Xubuntu 12.04* This is what I did after the installation: 1. sudo nano /etc/fstab 2. Removed SWAP entry 3. Saved 4. Rebooted 5. sudo apt-get install zram-config 6. http://i40.tinypic.com/n2cqq9.jpg I'm currently upgrading my system: sudo apt-get upgrade sudo apt-get dist-upgrade Now, Xubuntu 12.04 installation has NO Physical SWAP Partition. The SWAP that you see here: http://i40.tinypic.com/n2cqq9.jpg This is from zram-config http://en.wikipedia.org/wiki/ZRam https://launchpad.net/ubuntu/+source/zram-config *End of Test Report 1* Thank you for reading! -- All of us are smarter than any one of us. *Best Regards,* *amjjawad https://wiki.ubuntu.com/amjjawad/* *Start Ubuntuhttps://wiki.ubuntu.com/Lubuntu/CommunicationsTeam/WOWLubuntu/StartUbuntu * *My Own Business http://alilinx.blogspot.com/* I don't think that anyone says to run Xubuntu with 256MB RAM with no swap partition. I have volunteered to do this test because the Minimum System Requirement on the Website is not correct IMHO and as Lyz said, no one has done such test for a long time so I guess it is good to have some data regarding this. Creating a swap partition is a part of the standard install IIRC. Also, this can be a swap file
Pre-Alpha1 test reports.
Given that the current, aka good, Ubuntu ISO Tracker is not yet abailabe for daily test reports it was decided that we should use the one I did instead for a while until the good tracker is ready. So if you please and want to start doing tests and reporting them the Daily ISO Reporting Site, also DIRS, its on: http://79.99.1.99/~gridcube/ We should be doing this tests so we can have a good Alpha1 release. If you have any questions please do them. Thank you very much, and good luck with all those tests you are gonna do :D -- Bruno.- -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Pre-Alpha1 test reports.
UPDATE: The good tracker got updated just a few hours after this message was posted, it should be used instead: http://91.189.93.73/ sorry for the inconveniences -- Forwarded message -- From: Bruno Benitez gridc...@gmail.com Date: 2011/11/27 Subject: Pre-Alpha1 test reports. To: Xubuntu Development Discussion xubuntu-devel@lists.ubuntu.com Given that the current, aka good, Ubuntu ISO Tracker is not yet abailabe for daily test reports it was decided that we should use the one I did instead for a while until the good tracker is ready. So if you please and want to start doing tests and reporting them the Daily ISO Reporting Site, also DIRS, its on: http://79.99.1.99/~gridcube/ We should be doing this tests so we can have a good Alpha1 release. If you have any questions please do them. Thank you very much, and good luck with all those tests you are gonna do :D -- Bruno.- -- Bruno.- -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Daily Test - Desktop PC Intel x86 LiveCD-EntireDisk
As far as i know Xubuntu never had a Login sound. On Sun, Jun 5, 2011 at 3:36 AM, Unit 193 unit...@gmail.com wrote: Howdy folks! * No Login sound? I hope you can understand at least half of that :P ~Unit 193 - Alpine -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel -- Maik http://wearetechguys.comhttp://wearetechguys.com/forum/index.php%5DW.A.T.G.%5B/URL -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Daily Test - Desktop PC Intel x86 LiveCD-EntireDisk
Howdy folks! Here are some install notes (20110604): LiveCD: * File browser had some lag when I opened it * It thinks Boodle-VirtualBox is already on the network (It isn't...) * Shutdown was text only (LiveCD right after install) Install: * udev had a boot error (http://imgur.com/megcP ) * No Login sound? * 10 Updates * Doesn't tell you about a bad pass for Synaptic * Mouse disappears when you scroller click tab bar in firefox and thunar * Shutdown from GDM will give you text (No splash) I hope you can understand at least half of that :P ~Unit 193 - Alpine -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Daily Test - Desktop amd64 LiveCD-EntireDisk
Conducted daily test on Xubuntu Desktop amd64 LiveCD-EntireDisk. Install was done from initial menu, not desktop icon. Discepencies noted: http://iso.qa.ubuntu.com/qatracker/info/5786 Firefox: about:startpage - Not Found - The requested URL /11.10/Google was not found on this server. This error has been already noted (Bug #760910). drc -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Can't test anymore
Startup freezes, when there is keys: under Xubuntu logo. I tried using the older kernel 2.6.32-19-generic, but same thing. (I can reboot by pressing Alt-SysRq-S -U -B) -- http://www.iki.fi/8/ -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Xubuntu Intrepid Alpha 2 informal test
Hi Jeff, Big thanks for this report. It is greatly appreciated and indeed useful :-) On Tue, Jul 22, 2008 at 12:24 AM, Jeff Hanson [EMAIL PROTECTED] wrote: i386 Alternate CD HP Pavilion XG823 desktop, Celeron 700, 256MB, Nvidia MX440 All updates as of 20080721 installed via apt-get. Testing New Versions link at top of page doesn't jump: http://www.xubuntu.org/devel#testing Good catch. Thanks for fixing Vincent. :-) Testing section says see the Community Testing page which doesn't exist: https://wiki.ubuntu.com/Testing/Community See above. Favorite bug: bug# 247120 (dri2 missing) This bug was fixed in the package xorg-server - 2:1.4.99.906-1ubuntu1 Please confirm. Ghost line appeared in splash (picture attached). I've seen that too. I'll look for it again next reboot. Lets make a note to double check on this after we upload the new usplash theme. Lionel, Gauvain: Could either of you upload the new usplash theme? I'm not particular familiar with it. If you could document the procedure on the wiki somewhere, that would be great. If it is super simple, just give me a good head kick on IRC SVP. Movie player couldn't open 128-bit mp3 stream from Radio Wazee (http://wazee.org). Made several attempts. It does open the pls file and add the channels to the playlist. VLC succeeded. Manually installed liblame, gstreamer bad/ugly plugins, etc. Create archive in Thunar resulted in blank window after archive type selection (xsession-errors and screenshot attached). I hate to say this but could you try again now? I think we'll find we're lucky and it is fixd now :-) Quick search box in Synaptic is non-functional. I can confirm this. This appears to be intentionally. I'll seed apt-xapian-index so that we'll get this functionality since we don't have an issue with cd space atm. https://bugs.edge.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/250524 Gnash doesn't play anything on Youtube but the interactive chart on this page works: http://www.microsoft.com/windowsserver/compare/linux/windows-server-tco.mspx If Gnash depends on DRI2 then that could be the problem. Could you please file a bug? There appears to be useful info in xsession-errors_sysmon. System Monitor crashes when I select the File Systems tab (xsession-errors attached). This doesn't occur for me. Can you try again? :-) This is an informal test as I was just trying to verify that XFCE doesn't support the XDG menu specification correctly in regards to user submenu configurations. This makes applications installed by Wine end up in the Other submenu, including Wine Notepad which is included with the Wine package (screenshot attached). Same problem in Hardy. How is anyone going to believe that XFCE is a cheap Gnome clone when it can't even get the menus correct? :D haha :P Well, we're hoping this will be fixed for Intrepid in Xfce 4.6 :] -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel -- Cody A.W. Somerville Software Engineer Red Cow Marketing Technologies, Inc. Office: 506-458-1290 Toll Free: 1-877-733-2699 Fax: 506-453-9112 Cell: 506-449-5899 Email: [EMAIL PROTECTED] http://www.redcow.ca -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Xubuntu Intrepid Alpha 2 informal test
2008/7/22 Jeff Hanson [EMAIL PROTECTED] i386 Alternate CD HP Pavilion XG823 desktop, Celeron 700, 256MB, Nvidia MX440 All updates as of 20080721 installed via apt-get. Testing New Versions link at top of page doesn't jump: http://www.xubuntu.org/devel#testing Testing section says see the Community Testing page which doesn't exist: https://wiki.ubuntu.com/Testing/Community Hi, I've updated the website; could you report the other bugs at bugs.ubuntu.com? Thanks. (I've noticed the ghost throbber myself too btw) -- Vincent -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Xubuntu Intrepid Alpha 2 informal test
Charlie Kravetz wrote: Thanks for trying to make Xubuntu better. The website is being reviewed and will be corrected. Here is a correct link to the testing page: https://wiki.ubuntu.com/Xubuntu/Testing Noted. It will even more if you report the results of you testing here: https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo so that the other testers know to watch for these issues. Maybe next time. The tracker is at Alpha 3 and I have to deploy the system with Hardy soon. Could you file bug reports on these issues if there aren't any? This lets the developers see what is happening and helps them know what to fix. The Totem problem went away with more updates. I added Gnome to test bug #251337 (shutdown problem with ssh session active) and found that Gnome's mixer insisted on routing everything to the on-board piezo while XFCE worked correctly. (bug #251350). After adding ubuntu-desktop I don't have a splash screen anymore. Problem solved. :D The create archive problem also disappeared. I don't know if it's from an update or by adding ubunutu-desktop some dependency was fixed. Synaptic quick search problem previously reported as bug 244619. System Monitor File System tab crash went away. Xubuntu with Xfce has never tried to be a clone of the gnome desktop. I was joking. I observed the flame war a few months ago that Jono helped resolve so I know all about it. The XDG implementation problem affecting Wine is bug 250684. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Xubuntu Intrepid Alpha 2 informal test
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeff Hanson wrote: i386 Alternate CD HP Pavilion XG823 desktop, Celeron 700, 256MB, Nvidia MX440 All updates as of 20080721 installed via apt-get. Testing New Versions link at top of page doesn't jump: http://www.xubuntu.org/devel#testing Testing section says see the Community Testing page which doesn't exist: https://wiki.ubuntu.com/Testing/Community Favorite bug: bug# 247120 (dri2 missing) Ghost line appeared in splash (picture attached). Movie player couldn't open 128-bit mp3 stream from Radio Wazee (http://wazee.org). Made several attempts. It does open the pls file and add the channels to the playlist. VLC succeeded. Manually installed liblame, gstreamer bad/ugly plugins, etc. Create archive in Thunar resulted in blank window after archive type selection (xsession-errors and screenshot attached). Quick search box in Synaptic is non-functional. Gnash doesn't play anything on Youtube but the interactive chart on this page works: http://www.microsoft.com/windowsserver/compare/linux/windows-server-tco.mspx If Gnash depends on DRI2 then that could be the problem. System Monitor crashes when I select the File Systems tab (xsession-errors attached). This is an informal test as I was just trying to verify that XFCE doesn't support the XDG menu specification correctly in regards to user submenu configurations. This makes applications installed by Wine end up in the Other submenu, including Wine Notepad which is included with the Wine package (screenshot attached). Same problem in Hardy. How is anyone going to believe that XFCE is a cheap Gnome clone when it can't even get the menus correct? :D Thanks for trying to make Xubuntu better. The website is being reviewed and will be corrected. Here is a correct link to the testing page: https://wiki.ubuntu.com/Xubuntu/Testing It will even more if you report the results of you testing here: https://wiki.ubuntu.com/Xubuntu/Testing/TestingInfo so that the other testers know to watch for these issues. Could you file bug reports on these issues if there aren't any? This lets the developers see what is happening and helps them know what to fix. Xubuntu with Xfce has never tried to be a clone of the gnome desktop. Rather, it is a separate entity that may use some of gnome's software when it fits the mission. The Xubuntu development team defines the mission of Xubuntu in the following statement: quote * The goal of Xubuntu is to produce an easy to use distribution, based on Ubuntu, using Xfce as the graphical desktop, with a focus on integration, usability and performance, with a particular focus on low memory footprint. The integration in Xubuntu is at a configuration level, a toolkit level, and matching the underlying technology beneath the desktop in Ubuntu. Xubuntu will be built and developed as part of the wider Ubuntu community, based around the ideals and values of Ubuntu. Xfce4 is a lightweight desktop environment. Designed for productivity, it loads and executes applications quickly, while conserving system resources. Xfce4 has been supported in Ubuntu's universe since Hoary. In 2006, Xubuntu was born as a sibling of Ubuntu, Kubuntu, and Edubuntu. end quote - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIhe/3535p7ZS+ALgRAqweAJ9z+PK0JNd0nrFrq57LYVhgTxiGyQCgkMhu efuBm6A7vrPVLmNWGm9gEj4= =X1AD -END PGP SIGNATURE- -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Flat look (was: Re: Test the working GDM beta)
On Sun, Jul 13, 2008 at 4:54 AM, jmak [EMAIL PROTECTED] wrote: We have to decide, right now that we continue with the traditional design, or join in with unbuntu and kubuntu and choose a flat design. Those who don't know the differences here is a mockup that explains. http://img177.imageshack.us/img177/6897/flatnotflatlv7.png The main point with the flat design is not that trendy but rather it is more efficient from the visual point of view because it eliminates as much visual noises as possible. Note to everybody: we dont talk about personal preferences here but visual efficiency, unity and coherence of the desktop. If you comment please dont say, I like it or I dont like. Those are not arguments. Flat design sounds nice and clutter-free to me, but I would prefer to keep the visual distinction between the window and the window borders. It's hard to see where to grab the window when you want to drag and don't know about Alt+Drag. Cheers, -- Vincent -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Test the working GDM beta
On 7/13/08, Jim Campbell [EMAIL PROTECTED] wrote: On Sat, Jul 12, 2008 at 11:54 PM, jmak [EMAIL PROTECTED] wrote: Hello Jim, Nice work. I like it. I have one comment though. We have to decide, right now that we continue with the traditional design, or join in with unbuntu and kubuntu and choose a flat design. Those who don't know the differences here is a mockup that explains. http://img177.imageshack.us/img177/6897/flatnotflatlv7.png The main point with the flat design is not that trendy but rather it is more efficient from the visual point of view because it eliminates as much visual noises as possible. Note to everybody: we dont talk about personal preferences here but visual efficiency, unity and coherence of the desktop. If you comment please dont say, I like it or I dont like. Those are not arguments. I do like the visual coherency that ubuntu is taking. i tried using a blended-gtk wm theme (which provides that coherency / lack of gradient), but it doesn't feature all of the xfwm4 buttons, and I wanted to use a native xfwm4 window manager theme to accomodate all of the available wm buttons. Jim, Did you try the katiola window decoration? That is flat and have all the button functionality. Could you try modifying the theme, just to see, by changing the menu toolbar back to gray, like the rest and using the katiola window decorator. jmak I liked the slender and clean aspects of the daolo xfwm4 theme, but would prefer something that wasn't quite as bubbly, and something that could provide a gradient-free appearance - it's just that it's not as easy to create a wm theme as it is to modify the murrina theme elements (just editing the gtkrc file). We've got some time, though, we can figure something out. One more thing, the icons. Are we ever going to get rid of the tango icons? There are some icon themes on the wiki, what do you think about them? I haven't tried to install all of them. I tried downloading the black-white iconset, but it didn't get picked up by the desktop appearance app after I had extracted the tarball to my .themes folder. I had just selected the tango-noir icon set for that snapshot as the colors of the icons seemed complimentary to the rest of the theme that I had cobbled together. I do see tango-noir as being different from the regular tango icon set that we've had for the past several releases - I mean, at least the color scheme is different, and some of the actual icons (i.e., trash) are different, too. If you have any hex codes for the color elements that you've been using in your desings, could you post them to the wiki, perhaps as a sub-page to the /incoming page that is set up to display the sample artwork right now? It would be good to have those available as common elements, so that no other contributors are reinventing the wheel in working on color schemes. Thanks, Jmak! Jim -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Test the working GDM beta
Hi All, I've put together a working GDM based on Jozsef's artwork samples. You can download and use the tar.gz gdm theme archive from the Intrepid Artwork wiki page [1]. I've also put up a theme (screenshots on the same page) that I've worked on. It isn't finished, so thoughts, suggestions, comments are welcome. Jim [1] https://wiki.ubuntu.com/Xubuntu/Artwork/Incoming/Intrepid -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Test the working GDM beta
On 7/12/08, Jim Campbell [EMAIL PROTECTED] wrote: Hi All, I've put together a working GDM based on Jozsef's artwork samples. You can download and use the tar.gz gdm theme archive from the Intrepid Artwork wiki page [1]. I've also put up a theme (screenshots on the same page) that I've worked on. It isn't finished, so thoughts, suggestions, comments are welcome. Hello Jim, Nice work. I like it. I have one comment though. We have to decide, right now that we continue with the traditional design, or join in with unbuntu and kubuntu and choose a flat design. Those who don't know the differences here is a mockup that explains. http://img177.imageshack.us/img177/6897/flatnotflatlv7.png The main point with the flat design is not that trendy but rather it is more efficient from the visual point of view because it eliminates as much visual noises as possible. Note to everybody: we dont talk about personal preferences here but visual efficiency, unity and coherence of the desktop. If you comment please dont say, I like it or I dont like. Those are not arguments. One more thing, the icons. Are we ever going to get rid of the tango icons? There are some icon themes on the wiki, what do you think about them? jmak -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Test the working GDM beta
On Sat, Jul 12, 2008 at 11:54 PM, jmak [EMAIL PROTECTED] wrote: Hello Jim, Nice work. I like it. I have one comment though. We have to decide, right now that we continue with the traditional design, or join in with unbuntu and kubuntu and choose a flat design. Those who don't know the differences here is a mockup that explains. http://img177.imageshack.us/img177/6897/flatnotflatlv7.png The main point with the flat design is not that trendy but rather it is more efficient from the visual point of view because it eliminates as much visual noises as possible. Note to everybody: we dont talk about personal preferences here but visual efficiency, unity and coherence of the desktop. If you comment please dont say, I like it or I dont like. Those are not arguments. I do like the visual coherency that ubuntu is taking. i tried using a blended-gtk wm theme (which provides that coherency / lack of gradient), but it doesn't feature all of the xfwm4 buttons, and I wanted to use a native xfwm4 window manager theme to accomodate all of the available wm buttons. I liked the slender and clean aspects of the daolo xfwm4 theme, but would prefer something that wasn't quite as bubbly, and something that could provide a gradient-free appearance - it's just that it's not as easy to create a wm theme as it is to modify the murrina theme elements (just editing the gtkrc file). We've got some time, though, we can figure something out. One more thing, the icons. Are we ever going to get rid of the tango icons? There are some icon themes on the wiki, what do you think about them? I haven't tried to install all of them. I tried downloading the black-white iconset, but it didn't get picked up by the desktop appearance app after I had extracted the tarball to my .themes folder. I had just selected the tango-noir icon set for that snapshot as the colors of the icons seemed complimentary to the rest of the theme that I had cobbled together. I do see tango-noir as being different from the regular tango icon set that we've had for the past several releases - I mean, at least the color scheme is different, and some of the actual icons (i.e., trash) are different, too. If you have any hex codes for the color elements that you've been using in your desings, could you post them to the wiki, perhaps as a sub-page to the /incoming page that is set up to display the sample artwork right now? It would be good to have those available as common elements, so that no other contributors are reinventing the wheel in working on color schemes. Thanks, Jmak! Jim -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
Re: Test the working GDM beta
On Sun, Jul 13, 2008 at 12:32 AM, Jim Campbell [EMAIL PROTECTED] wrote: I haven't tried to install all of them. I tried downloading the black-white iconset, but it didn't get picked up by the desktop appearance app after I had extracted the tarball to my .themes folder. Oops, I meant, ~/.icons folder. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
** Changed in: python-pmw (Ubuntu) Status: In Progress = Fix Released -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
Please sponsor attached debdiff for willowng. ** Attachment added: willowng.debdiff http://launchpadlibrarian.net/12969226/willowng.debdiff ** Changed in: willowng (Ubuntu) Assignee: Albert Damen (albrt) = (unassigned) Status: In Progress = Confirmed -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
This bug was fixed in the package willowng - 0.3-0ubuntu2 --- willowng (0.3-0ubuntu2) hardy; urgency=low * debian/willowng.install: install files from python2.4 or python2.5 site-packages directory. Fixes FTBFS (LP: #204895). * Modify Maintainer value to match the DebianMaintainerField specification. -- Albert Damen [EMAIL PROTECTED] Sat, 29 Mar 2008 21:29:58 +0100 ** Changed in: willowng (Ubuntu) Status: In Progress = Fix Released ** Changed in: sqlrelay (Ubuntu) Status: In Progress = Fix Released -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
willowng: I have a package ready to upload already for this, but I want to check with amaranth first as he may want to do something more. ** Changed in: willowng (Ubuntu) Assignee: (unassigned) = Cesare Tirabassi (norsetto) Status: Confirmed = In Progress -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
Ah, sorry, I see Albert is working on this, so, never mind me, go on with his debdiff. ** Changed in: willowng (Ubuntu) Assignee: Cesare Tirabassi (norsetto) = (unassigned) Status: In Progress = Confirmed -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
This bug was fixed in the package sqlrelay - 1:0.38-3ubuntu1 --- sqlrelay (1:0.38-3ubuntu1) hardy; urgency=low * patches/fix-wnolongdouble.dpatch: Remove test for -Wno-long-double from configure and don't use this flag. The test succeeded but compiling failed. Fixes FTBFS (LP: #204895). * Create patches/00list and add fix-wnolongdouble to it. * debian/rules: Add fix-wnolongdouble to debian_patches. * debian/control: - Add dpatch to Build-Depends - Modify Maintainer value to match the DebianMaintainerField specification. -- Albert Damen [EMAIL PROTECTED] Sat, 29 Mar 2008 20:12:11 +0100 -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
Please sponsor the attached debdiff for enthought-traits. The package builds and installs fine in a Hardy pbuilder. To prevent an installation error about missing files, the removal of the nspkg.pth files had to be done before dh_pycentral is called. ** Attachment added: enthought-traits.debdiff http://launchpadlibrarian.net/12971681/enthought-traits.debdiff ** Changed in: enthought-traits (Ubuntu) Status: New = Confirmed -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
Sorry, that was not good yet. Will complete this tomorrow. ** Changed in: enthought-traits (Ubuntu) Assignee: (unassigned) = Albert Damen (albrt) Status: Confirmed = In Progress ** Changed in: enthought-traits-ui (Ubuntu) Assignee: (unassigned) = Albert Damen (albrt) Status: New = In Progress ** Attachment removed: enthought-traits.debdiff http://launchpadlibrarian.net/12971681/enthought-traits.debdiff -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
** Changed in: wxglade (Ubuntu) Assignee: (unassigned) = Chris Brotherton (protonchris) Status: New = In Progress -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
Looks like a new version of wxglade was just added to debian: http://packages.debian.org/changelogs/pool/main/w/wxglade/current/changelog The new debian package also appears to fix the python-central issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472037 I will examine the differences in the current ubuntu package and the new debian package more closely tomorrow. -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
This bug was fixed in the package enthought-traits - 2.0.1b1-2ubuntu1 --- enthought-traits (2.0.1b1-2ubuntu1) hardy; urgency=low * debian/rules: - Update SITE_PACKAGES to match the new python-central directory structure. Fixes FTBFS (LP: #204895). - Move removal of nspkg.pth files from binary-predeb to python-install target, to prevent installation errors. * debian/control: - Bump minimum version of python-central to 0.6. - Modify Maintainer value to match the DebianMaintainerField specification. -- Albert Damen [EMAIL PROTECTED] Sat, 29 Mar 2008 21:52:03 +0100 ** Changed in: enthought-traits (Ubuntu) Status: In Progress = Fix Released -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
Please sponsor attached debdiff for enthought-traits-ui. It builds and installs fine in a Hardy pbuilder. ** Attachment added: enthought-traits-ui.debdiff http://launchpadlibrarian.net/12977173/enthought-traits-ui.debdiff ** Changed in: enthought-traits-ui (Ubuntu) Assignee: Albert Damen (albrt) = (unassigned) Status: In Progress = Confirmed -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
This bug was fixed in the package enthought-traits-ui - 2.0.1b1-3ubuntu1 --- enthought-traits-ui (2.0.1b1-3ubuntu1) hardy; urgency=low * debian/rules: - Update SITE_PACKAGES to match new python-central directory structure. Fixes FTBFS (LP: #204895). - Remove nspkg.pth files in python-install target instead of binary-predeb target, to prevent installation errors. - Do not remove /usr/lib, this is now handled by python-central. * debian/control: - Bump minimum version of python-central to 0.6. - Modify Maintainer value to match the DebianMaintainerField specification. -- Albert Damen [EMAIL PROTECTED] Sun, 30 Mar 2008 14:25:23 +0200 ** Changed in: enthought-traits-ui (Ubuntu) Status: Confirmed = Fix Released -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
Merge from debian unstable for wxglade. ** Attachment added: wxglade_0.6.3-0.1ubuntu1.diff.gz http://launchpadlibrarian.net/12979016/wxglade_0.6.3-0.1ubuntu1.diff.gz -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
** Changed in: wxglade (Ubuntu) Status: In Progress = Fix Released -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
Speech-dispatcher has already been fixed, just after the build failure reported on ubuntuwire. It builds fine in a Hardy pbuilder. speech-dispatcher (0.6.6-0ubuntu5) hardy; urgency=low * debian/patches/05_honour-environment.dpatch: Drop for now, proper integration work will be done in Intrepid. * debian/speech-dispatcher.profile.d: Drop, same as above. * Run as system service by default, this will change for intrepid. * debian/rules: Adjust for recent pycentral updates. -- Luke Yelavich [EMAIL PROTECTED] Wed, 05 Mar 2008 13:48:11 +1100 ** Changed in: speech-dispatcher (Ubuntu) Status: New = Invalid -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
** Changed in: wxwidgets2.6 (Ubuntu) Status: New = Invalid -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
** Also affects: enthought-traits-ui (Ubuntu) Importance: Undecided Status: New -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
[Bug 204895] Re: Packages failed archive rebuild test possibly due to python-central transition
** Also affects: python-pmw (Ubuntu) Importance: Undecided Status: New ** Changed in: python-pmw (Ubuntu) Assignee: (unassigned) = Scott Kitterman (kitterman) Status: New = In Progress -- Packages failed archive rebuild test possibly due to python-central transition https://bugs.launchpad.net/bugs/204895 You received this bug notification because you are a member of Xubuntu Team, which is subscribed to exo in ubuntu. -- xubuntu-devel mailing list xubuntu-devel@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/xubuntu-devel
