Re: PackageKit: Call for testing
Am Dienstag, den 02.09.2008, 23:50 -0500 schrieb Luke L: It's packagekit-gnome, not 'gnome-packagekit'. Worked fine for me. Are we supposed to be critiquing the software? It was a bit minimalist, and the frames in the windows are not resize-able. It doesn't seem as full featured as Synaptic, though it has a good look to it. It's info area is better laid out, and a live search feature. The repo listing is better in Synaptic. In short, I could see it being very useful and competitive with Synaptic, with a few tweaks and cleanups. Currently it is not the question if to replace our existing tools. But it is important to not miss the PackageKit interface on APT based systems, since some upstream projects think about using it for installing additional components. Furthermore PackageKit only wants to target simply package manupiulation tasks. It will never be a replacement for Synaptic, but could be used in the language selector or gnome-app-install. Cheers, Sebastian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Intrepid compatibility with C3 CPUs
Olá Oliver e a todos. On Tuesday 02 September 2008 13:28:56 Oliver Grawert wrote: [EMAIL PROTECTED]:~$ grep CONFIG_M586 /boot/config-2.6.27-2-generic CONFIG_M586=y # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MGEODE_LX is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_MVIAC7 is not set # CONFIG_MPSC is not set # CONFIG_MCORE2 is not set Linux blubug 2.6.27-1-generic #1 SMP Sat Aug 23 23:19:01 UTC 2008 x86_64 GNU/Linux cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz stepping: 6 cpu MHz : 1200.000 cache size : 3072 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 2 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm bogomips: 4788.01 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T8300 @ 2.40GHz stepping: 6 cpu MHz : 1200.000 cache size : 3072 KB physical id : 0 siblings: 2 core id : 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr sse4_1 lahf_lm bogomips: 6703.26 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: -- BUGabundo :o) (``-_-´´) http://LinuxNoDEI.BUGabundo.net Linux user #443786GPG key 1024D/A1784EBB My new micro-blog @ http://BUGabundo.net ps. My emails tend to sound authority and aggressive. I'm sorry in advance. I'll try to be more assertive as time goes by... signature.asc Description: This is a digitally signed message part. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Bugs introduced in GCC?
On Tue, Sep 02, 2008 at 10:41:49PM -0400, Richard M. Stallman wrote: In terms of actual volume of patches against upstream, and excluding SVN updates, the diff from the base Debian 4.2.3-2 version and Ubuntu 8.04's 4.2.3-2ubuntu7 is about 40 KB. If so, what is it meant to change? Matthias (CCed) should be able to give more information on any particular patches that are of concern. I didn't even imagine trying to read them myself! My apologies for being vague; I wanted to reply to you, but didn't have anything like a reasonable summary of all the Debian/Ubuntu changes to hand. It sounded like your direct concerns were the apparent volume and this specific bug, anyway. However, I've just found the summary, which is in /usr/share/doc/gcc-4.2-base/README.Debian.gz in the built binary packages. It follows for your convenience in case you're interested. Patches that Ubuntu applied in this version: svn-updates: updates from the 4.2 branch upto 20080329. svn-doc-updates: updates from the 4.2 branch upto 20080308 (documentation). rename-info-files: Allow transformations on info file names. Reference the transformed info file names in the texinfo files. gcc-directives-only-doc: Backport from trunk: -fdirectives-only (when preprocessing, handle directives, but do not expand macros). documentation changes sparc-niagara2-doc: Add niagara2 optimization support i386-biarch-doc: biarch patches for i386/x86_64 gcc-version: Add package identification to the gcc version string gcc-textdomain: Set gettext's domain and textdomain to the versioned package name. gcc-driver-extra-langs: Add options and specs for languages that are not built from a source (but built from separate sources). gcc-hash-style-both: Link using --hash-style=both (alpha, amd64, ia64, i386, powerpc, ppc64, s390, sparc) libstdc++-pic: Build and install libstdc++_pic.a library. libstdc++-doclink: adjust hrefs to point to the local documentation libstdc++-doxygen: libstdc++ doxygen docs: Set SHORT_NAMES to YES libjava-stacktrace: libgcj: Lookup source file name and line number in separated debug files found in /usr/lib/debug libjava-subdir: - Set the libjava sublibdir to /usr/lib/gcj-4.2 - Set the default libgcj database dir to /var/lib/gcj-4.2 libjava-jnipath: - Add /usr/lib/jni to java.library.path. - When running the i386 binaries on amd64, look in - /usr/lib32/gcj-x.y and /usr/lib32/jni instead. libjava-sjlj: Don't try to use _Unwind_Backtrace on SJLJ targets. See bug #387875, #388505, GCC PR 29206. libjava-rpath: - Link ecjx and gij with -rpath $(dbexecdir) libjava-jar: gjar: support @ arguments. libjava-nojavac: libjava/classpath: Don't require javac without java maintainer mode. libjava-armel-ldflags: Adjust libjava extra_ldflags for armel. libjava-xulrunner1.9: Add configure check for xulrunner-1.9. libffi-configure: Add --enable-libffi option to toplevel configure script pr20218: Backport from mainline for PR middle-end/17982, PR middle-end/20218. pr20218-mips: Backport from mainline for PR middle-end/20218, mips part. pr28102: Apply proposed fix for PR target/28102. pr22244: Improve debug info for packed arrays with constant bounds (PR fortran/22244) pr30961: your description libgcc-tramp-ppc32: Fix libgcc.a(tramp.o) on ppc32 gcc-directives-only: Backport from trunk: -fdirectives-only (when preprocessing, handle directives, but do not expand macros). sparc-niagara2: Add niagara2 optimization support alpha-no-ev4-directive: boehm-gc-nocheck: Disable running the boehm-gc testsuite. Hangs the buildd at least on hppa. boehm-gc-getnprocs: boehm-gc/pthread_support.c (GC_get_nprocs): Use sysconf as fallback. note-gnu-stack: Add .note.GNU-stack sections for gcc's crt files, libffi and boehm-gc Taken from FC. arm-pr28516: Fix PR28516 on ARM arm-pr30486: Fix 30486 on ARM arm-unbreak-eabi-armv4t: Fix armv4t build on ARM hurd-profiling: Fix profiling on hurd-i386. hurd-fast-math: Support -ffast-math on hurd-i386. m68k-fjump: gcc/config/m68k/m68k.md: always use as fjcc pseudo op, we rely heavily on as to generate the right size for the jump instructions fixes #359281 m68k-save_pic: gcc/config/m68k/m68k.c: correctly save the pic register, when not done by reload() (fixes _Unwind_RaiseException and thus exception handling) fixes 345574 m68k-dwarf: correct the dwarf frame information, but preserve compatibility m68k-split_shift: use correct predicates for long long shifts and use more splits fixes 381572 m68k-limit_reload: correctly limit reload class fixes 375522 m68k-prevent-qipush: prevent combine from creating a byte push on the stack (invalid on m68k) m68k-return: don't use single return if fp register have to be restored fixes 386864 m68k-jumptable: Don't force byte offset when accessing the jumptable, gas can generate the correct
Re: CDBS and upstream changelogs
On Tuesday 02 September 2008 15.48.22 Martin Pitt wrote: We deliberately made this change in order to save several Megabytes on the CDs, which are better spent for more useful things. You don't have to download the entire source package, usually the upstream home pages have an online accessible changelog. That is not a very helpful suggestion at all. All upstream home pages are different, so I would have to search in different ways for every package. That is as convenient as joining all upstream -announce lists, idle on all IRC channels etc. Not having to do things like that is a big point with using a distribution. So I very much prefer for Ubuntu to include the upstream changelog in a standardized place. When a package is updated to a new upstream version the upstream changelog is often far more interesting for me than debian/changelog. Also, in many cases a summary of the interesting upstream changes are echoed in the package changelog (debian/changelog). I have not studied this carefully, but I think most just say: * New upstream release. That is often followed by a list of closed bugs. But that only gives information about a few fixed problems that have been reported to Ubuntu/Debian, not all fixes and definitely not new features. So disabling CDBS automatic handling of this looks like an obvious policy violation to me. I don't agree. Normal debhelper doesn't install upstream changelogs by default either, and cdbs doesn't stop you from doing it, it just doesn't do it by default (as in Debian). Yes, I was wrong. The modification is not a policy violation in itself. However a CDBS with this modification will build policy violating packages where the unmodified version will not. That you can force cdbs to include the upstream changelog doesn't really matter as many DD's probably don't do this. Why should they, when CDBS already includes the files automatically? Right, that was the intention. Syncing a source package from Debian to Ubuntu will cause a lot of other hidden changes, such as toolchain hardening, translation stripping, gettext support for .desktop files, and all that. The great thing about cdbs is that we can make those changes centrally and document them there, instead of spreading them over hundreds of source packages and constantly being inconsistent (of course that doesn't apply to all packages which don't use cdbs). Your examples are mainly for added stuff, not removed stuff. Of course I realize that a rebuilt package will not be exactly identical. But where is this central change documented? It sounds like there have been a decision made that Ubuntu packages does not have to include upstream changelogs. Before sending my original message I searched the archive of various mailing lists as well as bugs against CDBS on launchpad, but found nothing. The only thing I found was Debian Policy, which clearly states the opposite. That upstream changelogs should be included as changelog.gz. The chapter (12.7) I included have not been changed in the recently posted Ubuntu Policy either. How much space does this really save on the CDs? Back then, when we made the change, we rebuilt some 10 packages too free several MB. It's difficult to measure the savings for all packages using cdbs, but I guesstimate an magnitude of 10 MB. Was that only from the upstream changelogs? The reason I ask is that the same CDBS version made several other very nice space saving changes by symlinking identical files. But even if 10MB is correct I don't think that is justification enough for removing such useful documentation. When thinking about this during the last day I have gotten a few other ideas that might be worth considering to save space. These are not really related to the upstream changelog issue, but I am to lazy to send a separate e-mail. :-) 1. Remove very old entries from debian/changelog. Pick a good time and only include entries newer than that, maybe the previous LTS (dapper) might be a good cutoff time? People who need to look at older entries than that can download the source or go to launchpad. 2. Keep as much documentation files as possible unzipped on the CDs and gzip them during installation. This should improve squashfs compression a lot. 3. If 2 is not an option, then maybe change Ubuntu Policy and allow something other than gzip. bzip2 or lzma usually compress much better, but probably most of the files are too small for this to really make a difference. Best regards, Pär Andersson signature.asc Description: This is a digitally signed message part. -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
