Re: x86 buildd for experimental ?
On Wed, Jan 24, 2007 at 10:06:05AM +0100, Marc 'HE' Brockschmidt <[EMAIL PROTECTED]> wrote: > Mike Hommey <[EMAIL PROTECTED]> writes: > > On Wed, Jan 24, 2007 at 12:18:48AM +0100, Martin Zobel-Helas <[EMAIL > > PROTECTED]> wrote: > >> On Tue Jan 23, 2007 at 20:51:27 +0100, Mike Hommey wrote: > >>> (More than a few days later, it seems like still nothing is > >>> happening...) > >> i can see a couple of logs signed by Marc, so what do you complain about > >> exactly? Marc is working on all packages from experimental, though it > >> might take a while to build all packages in the right order do get all > >> packages (like gnome 2.10) compiled in the right order. > > I would assume 10 days is enough to "automatically" build all that > > is in experimental... > > It is. The missing packages are FTBFS due to insufficient > build-dependencies. The build-logs for all packages are, as advertised, > on experimental.debian.net. > > All packages that can be autobuilt on i386 have been autobuilt, and that > was finished more than a week ago. But nice to hear that "nothing" has > happened. Sadly enough, it seems gnome-panel, gnome-terminal, epiphany-extensions, gnome-applets, file-roller, gedit, gnome-session, yelp, metacity and some others can't be autobuilt. Well, then, I'm going to build and upload them. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Language on short descriptions
Reading devel-changes I came across this dahb-html package and not understanding the short description I had to go and do an apt-cache show to get out of my curiosity, which I found rather annoying. On Sat, Feb 03, 2007 at 08:32:04PM +, Daniel Baumann wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Format: 1.7 > Date: Sat, 3 Feb 2007 20:31:00 +0100 > Source: dahb-html > Binary: dahb-html > Architecture: source all > Version: 3.1.2.18-1 > Distribution: unstable > Urgency: low > Maintainer: Daniel Baumann <[EMAIL PROTECTED]> > Changed-By: Daniel Baumann <[EMAIL PROTECTED]> > Description: > dahb-html - Debian GNU/Linux Anwenderhandbuch > Changes: > dahb-html (3.1.2.18-1) unstable; urgency=low > . >* New upstream release. > Files: > 58766eb89d73b03f43d524e14c999028 577 non-free/doc optional > dahb-html_3.1.2.18-1.dsc > 2e5070ae2f22a11c07343d7c095de915 20103570 non-free/doc optional > dahb-html_3.1.2.18.orig.tar.gz > 845079ff3b5b662a55eb72ab2cc09749 6920 non-free/doc optional > dahb-html_3.1.2.18-1.diff.gz > 712200e627ec806506446298571814a7 20136270 non-free/doc optional > dahb-html_3.1.2.18-1_all.deb > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFFxOb0+C5cwEsrK54RAtB3AJ4yIFrPRHFoI8Ss2pCHmqdlhJ0D+gCgiPzL > /yhdqBWAdqIx8P46b05h5vY= > =jMLE > -END PGP SIGNATURE- I'd recommend at least english translation in parenthesis to avoid this kind of confusions. What do others think about this? Is it worth even a wishlist bug? Now, I guess that Anwenderhandbuch means Handbook. Daniel I'd, particulary like to hear your opinion on this and why you decided to put it in German. Did you think it was clear enough? or that it didn't care since the package was german-speaking people oriented? Hope to help, -- Damián Viano(Des) ¯ ¯ - _ _ - ¯ ¯ GPG: 0x6EB95A6F Debian ¯-_GNU_-¯ Linux Web: http://damianv.com.ar/ ¯-¯ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: x86 buildd for experimental ?
On Sun, Feb 04, 2007 at 09:43:33AM +0100, Mike Hommey <[EMAIL PROTECTED]> wrote: > On Wed, Jan 24, 2007 at 10:06:05AM +0100, Marc 'HE' Brockschmidt <[EMAIL > PROTECTED]> wrote: > > Mike Hommey <[EMAIL PROTECTED]> writes: > > > On Wed, Jan 24, 2007 at 12:18:48AM +0100, Martin Zobel-Helas <[EMAIL > > > PROTECTED]> wrote: > > >> On Tue Jan 23, 2007 at 20:51:27 +0100, Mike Hommey wrote: > > >>> (More than a few days later, it seems like still nothing is > > >>> happening...) > > >> i can see a couple of logs signed by Marc, so what do you complain about > > >> exactly? Marc is working on all packages from experimental, though it > > >> might take a while to build all packages in the right order do get all > > >> packages (like gnome 2.10) compiled in the right order. > > > I would assume 10 days is enough to "automatically" build all that > > > is in experimental... > > > > It is. The missing packages are FTBFS due to insufficient > > build-dependencies. The build-logs for all packages are, as advertised, > > on experimental.debian.net. > > > > All packages that can be autobuilt on i386 have been autobuilt, and that > > was finished more than a week ago. But nice to hear that "nothing" has > > happened. > > Sadly enough, it seems gnome-panel, gnome-terminal, epiphany-extensions, > gnome-applets, file-roller, gedit, gnome-session, yelp, metacity and > some others can't be autobuilt. To be fair, some of these have build dependencies problems. But I could build metacity and gnome-session... Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409627: ITP: vim-addon-manager -- command line manager of Vim addons
Package: wnpp Severity: wishlist Owner: Stefano Zacchiroli <[EMAIL PROTECTED]> * Package name: vim-addon-manager Version : 0.1 Upstream Author : Stefano Zacchiroli <[EMAIL PROTECTED]> * URL : svn://svn.debian.org/svn/pkg-vim/trunk/packages/vim-addon-manager * License : GPL Programming Lang: Ruby Description : command line manager of Vim addons vim-addon-manager is a tool for managing addons for the Vim editor. . Using the vim-addons command line the user can list the addons installed on its system (i.e. which are registered in the vim addons registry) and install or uninstall each of them in its per-user configuration directory (~/.vim). . Override of addons which are enabled per default on the system, so that they are not enabled for the current user, is possible too. Draft packages are available at http://people.debian.org/~zack/vim/. Comments are welcome, especially on both the descriptions above and my ruby-related choices, since I'm not familiar with any ruby specific packaging issues. Cheers. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
X and non-X packages (Re: Attempts at security)
> From: Lars Wirzenius > Newsgroups: gmane.linux.debian.devel.general > Subject: Re: Attempts at security > Date: Sat, 03 Feb 2007 14:05:30 + Hallo. > On la, 2007-02-03 at 12:37 +0100, Hendrik Sattler wrote: >> > > Not being able to change the cause to the better doesn't mean to >> > > introduce a mess to control the result. And I really hope that Debian >> > > never considers installing+enabling selinux by default. >> > >> > IIRC, debian/etch already does already install selinux today without you >> > even noticing it. >> >> It is not enabled by default. That is the other point: you get that selinux >> integration if you want or not. > > Debian has made similar decisions throughout its history: we generally > don't provide separate X and non-X versions of the same package, for > packages where this is a build time option, for example. That is also a > cost every Debian user pays: increased disk and memory usage, even if > they don't use X at all. I'm the one, who don't need X, but emacs21 is linked to some X, even to (ugly) 3d scollbars, that i hate. Thus, i whould say it's a *very* big disadvantage. Also i want to ask, if you don't mind. Thanks. While there are plenty of possibilities to contribute to Debian as whole, and in particular, it's very hard for me to even build package with `apt-get source && debian/rules build`. If there are documents on topic of configuring self build packages, please point them to me. But i would really like to have something, like ,-*- |package-0.1.7: $ ./debian/rules help `-*- very brief description how to configure, build package, or to have maintainer's configuration to play with (if this information isn't KNOW-HOW ;). apt-build is debian's version of gentoo-like philosophy, and i would like to have it fully used by me. > In order to keep the complexity of the entire Debian system manageable, > we need to make those choices. If we, as a project, are of the opinion > that providing SELinux support is a good thing, then everything in > Debian that needs to be changed for the support to exist needs to be > changed, even if the individual maintainer thinks SELinux isn't useful. As there are *-static and non static packages of executable, e2fsck as example, i think, it's not very hard to have some other differences, such as *-x -nox, etc. As for SELinux and other security stuff, as it was mentioned in lkml, security requires money (big money). But if users of offtopic system are using Administrator, as they want to have only Word && solitaire, and time of half-oses, like Win9X, passed, it's their problems with security and stuff, like having passwords sticking on the screen. I'm not admin of server fields, but my opinion f.e. on openssh-server's default config with "rootlogins: on" is bad, also, i've found that to have numerous configuration for it is very difficult, due to how /etc/init.d/ssh is written (my laptop and server are with real IPs, and to have dummy ssh:22 as good idea, also to have 2-3 dummies around real one on some other port is very good (as logs say) obscurity ;) As for execsheild, vDSO address space randomization and stuff like this, software was buggy long before that features were implemented (famous bind, sendmail etc.), thus i wouldn't rely strongly on it. Kind regards. -- -o--=O`C #oo'L O <___=E M -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409640: ITP: mafft -- Multiple alignment program for amino acid or nucleotide sequences
Package: wnpp Severity: wishlist Owner: Charles Plessy <[EMAIL PROTECTED]> Package name: mafft Version : 6.236 Upstream Author : Kazutaka Katoh <[EMAIL PROTECTED]> URL : http://align.bmr.kyushu-u.ac.jp/mafft/software/ License : BSD Programming Lang: C Description : Multiple alignment program for amino acid or nucleotide sequences MAFFT is a multiple sequence alignment program for unix-like operating systems. It offers a range of multiple alignment methods, L-INS-i (accurate; recommended for <200 sequences), FFT-NS-2 (fast; recommended for >2,000 sequences), etc. MAFFT was non-free, but Version 6.233 and later are distributed under the BSD license. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-2-powerpc64 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409639: ITP: jp2a -- converts jpg images to ascii
Package: wnpp Severity: wishlist Owner: Joao Eriberto Mota Filho <[EMAIL PROTECTED]> * Package name: jp2a Version : 1.0.6 Upstream Author : Christian Stigen Larsen <[EMAIL PROTECTED]> * URL : http://csl.sublevel3.org/jp2a * License : GPL Programming Lang: C Description : converts jpg images to ascii Small utility that converts JPG images to ASCII using libjpeg. jp2a is very flexible. It can use ANSI colors and html in output. URL: http://csl.sublevel3.org/jp2a -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=pt_BR, LC_CTYPE=pt_BR (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: nsswitch.conf
Hi, On Sun, Feb 04, 2007, Brian May wrote: > Is it still the case that packages should not update > /etc/nsswitch.conf as documented in bug #78110? I don't think #78110 states that packages should not update /etc/nsswitch.conf and #78110 has its youngest message in the previous century. :) > The reason I ask is because libnss-mdns does just > this (e.g. see bug #406198), and I thought this > was a policy violation. #406198 is about reverting the changes it does to nsswitch.conf on removal, not about not updating nsswitch.conf, but yes, libnss-mdns edits the conffile of another package. Before the auto-updating, another solution was chosen which was to list mdns in the nsswitch.conf conffile (see base-files 3.1.8) but this was reverted due to various issues (see 3.1.10) and nsswitch.conf isn't a conffile since 3.1.11 precisely to permit updating: see #348580. (The issues for the reversal in 3.1.10 were: - reference to a non-base lib in a base package - exact configuration of mdns and place of mdns in nsswitch.conf didn't reach a consensus) I don't think the very special case in which libnss-mdns lies will ever be covered by policy, and I think this is the best which can be achieved for now. If you have proposals to automatically integrate mdns without touching the file, it would be interesting to dicsuss them and perhaps propose any relevant infrastructure to -- say -- the glibc package for example. > My personal opinion is that I consider /etc/nsswitch.conf, like > /etc/network/interfaces, a file reserved for local administrators and > changing the fundamental polices of the computer because some package > the administrator never heard of before was automatically pulled into > the upgrade process is not a good thing. It is one way of seeing it, however you've got to see it from the other way as well: how is it possible to integrate a new type of lookup (mDNS) on desktop machines which want RendezVous / UPnP / mDNS to work? People at which we target mDNS usage could be you and me, but I don't think we want to request every current and future user of libnss-mdns to edit nsswitch.conf before it works; we're talking about a package installed by default on the default desktop. And even I wouldn't like being bothered to hand-edit nsswitch.conf. > (not to mention mdns breaks anybody who used the recommendations of a > draft Internet standard[1] to name local computers as documented > already in numerous bug reports) This is a separate issue. You can blame mDNS for not keeping backward compatibility with existing networks using .local, but it is a fact that wont change, and yes, it is fundamentally incompatible to mix mDNS and regular DNS on a network which has a .local TLD. However, please note that libnss-mdns can be pulled and should not prevent regular DNS from working on such a network: libnss-mdns basically forwards all its mDNS queries to avahi-daemon and avahi-daemon will disable itself when it detects a .local SOA. This means mDNS wont work on such networks, but DNS should continue working as it was. Bye, -- Loïc Minier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#409640: ITP: mafft -- Multiple alignment program for amino acid or nucleotide sequences
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/04/07 08:27, Charles Plessy wrote: > Package: wnpp > Severity: wishlist > Owner: Charles Plessy <[EMAIL PROTECTED]> > > Package name: mafft > Version : 6.236 > Upstream Author : Kazutaka Katoh <[EMAIL PROTECTED]> > URL : http://align.bmr.kyushu-u.ac.jp/mafft/software/ > License : BSD > Programming Lang: C > Description : Multiple alignment program for amino acid or nucleotide > sequences > > MAFFT is a multiple sequence alignment program for unix-like operating > systems. It offers a range of multiple alignment methods, L-INS-i > (accurate; recommended for <200 sequences), FFT-NS-2 (fast; recommended > for >2,000 sequences), etc. What do you use for nucleotides between 200 and 2000 sequences? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFxhJES9HxQb37XmcRAkFrAKC2LbgbUvF6ukVKiS5VsnWvc8JL9wCggxAE ATbU9r9o78P5/Rd03RBQh3Q= =hk0b -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#409640: ITP: mafft -- Multiple alignment program for amino acid or nucleotide sequences
On Sun, Feb 04, 2007, Ron Johnson wrote: > > MAFFT is a multiple sequence alignment program for unix-like operating > > systems. It offers a range of multiple alignment methods, L-INS-i > > (accurate; recommended for <200 sequences), FFT-NS-2 (fast; recommended > > for >2,000 sequences), etc. > What do you use for nucleotides between 200 and 2000 sequences? I don't know anything about nucleotides, but I suppose you can use either of the two methods... -- Loïc Minier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X and non-X packages (Re: Attempts at security)
Am Sonntag 04 Februar 2007 15:36 schrieb Oleg Verych: > I'm the one, who don't need X, but emacs21 is linked to some X, even to > (ugly) 3d scollbars, that i hate. Thus, i whould say it's a *very* big > disadvantage. emacs21-nox exists and that's what I use, too. The X interface is plain ugly and has an incredibly bad usability. Using the terminal interface has the advantage of being the same for remote shell access. It's just about copying a sensible configuration file (I doubt that the terminals that the default is for are still widely used). HS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X and non-X packages (Re: Attempts at security)
On 04-Feb-07, 08:36 (CST), Oleg Verych <[EMAIL PROTECTED]> wrote: > As there are *-static and non static packages of executable, e2fsck as > example, i think, it's not very hard to have some other differences, > such as *-x -nox, etc. There are a very few packages built -static: all I can find at present are xlibs-dev (?), e2fsck, bash, busybox, dar, and two versions of zsh. We used to build -x and -nox versions of packages that supported it; it became a huge bloat and workload and we agreed to stop. Steve -- Steve Greenland The irony is that Bill Gates claims to be making a stable operating system and Linus Torvalds claims to be trying to take over the world. -- seen on the net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#409640: ITP: mafft -- Multiple alignment program for amino acid or nucleotide sequences
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/04/07 12:13, Loïc Minier wrote: > On Sun, Feb 04, 2007, Ron Johnson wrote: >>> MAFFT is a multiple sequence alignment program for unix-like operating >>> systems. It offers a range of multiple alignment methods, L-INS-i >>> (accurate; recommended for <200 sequences), FFT-NS-2 (fast; recommended >>> for >2,000 sequences), etc. >> What do you use for nucleotides between 200 and 2000 sequences? > > I don't know anything about nucleotides, but I suppose you can use > either of the two methods... I was wondering if OP made a typo somewhere. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFxjXMS9HxQb37XmcRAl+rAJ9uMulXyLCtTIk0Fv4hVdLMI2FwZACgqPc8 PHWU3DuzDPEQosDCaMCPH8Y= =JWR0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X and non-X packages (Re: Attempts at security)
> From: Hendrik Sattler > Newsgroups: gmane.linux.debian.devel.general > Subject: Re: X and non-X packages (Re: Attempts at security) > Date: Sun, 4 Feb 2007 18:59:01 +0100 Hallo, Hendrik. > Am Sonntag 04 Februar 2007 15:36 schrieb Oleg Verych: >> I'm the one, who don't need X, but emacs21 is linked to some X, even to >> (ugly) 3d scollbars, that i hate. Thus, i whould say it's a *very* big >> disadvantage. > > emacs21-nox exists > and that's what I use, too. The X interface is plain ugly and has an > incredibly bad usability. Using the terminal interface has the advantage of > being the same for remote shell access. It's just about copying a sensible > configuration file (I doubt that the terminals that the default is for are > still widely used). Really, it is. Somehow i didn't find it in apt-cache before ;D > HS > > Thanks ! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409740: ITP: python-guppy -- object and heap memory sizing, profiling and analysis in Python
Package: wnpp Severity: wishlist Owner: Yaroslav Halchenko <[EMAIL PROTECTED]> * Package name: python-guppy Version : 0.1.6 Upstream Author : Sverker Nilsson <[EMAIL PROTECTED]> * URL : http://guppy-pe.sourceforge.net * License : MIT Programming Lang: Python, C Description : object and heap memory sizing, profiling and analysis in Python Guppy-PE is a programming environment providing object and heap memory sizing, profiling and analysis. It includes a prototypical specification language that can be used to formally specify aspects of Python programs and generate tests and documentation from a common source. Modules which constitute the environment: - Heapy: debugging and optimization regarding memory related issues in Python programs - GSL (Guppy Specification Language): describes aspects of a system, especially its API, in a way that can be automatically converted to tests as well as to documents - Guppy: umbrella package combining Heapy and GSL with support utilities such as the Glue module that keeps things together. Comments: Heapy is somewhat an alternative to pysizer (http://pysizer.8325.org), which unfortunately wasn't developed recently. That is why I ITP guppy in favor over pysizer at the moment. I am still not sure what name should be. Debian python policy advises (uses verb "should", not "must") to use python-MODULE package name for public modules. But I am not sure if python- prefix is still worth its use, since we have debtags now. So at the end bin package name might simply change to guppy or guppy-pe. Any advice is welcome. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (990, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-686 Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
