creating init.d scripts

2011-08-31 Thread Russell Coker
We have had a discussion about theoretical issues related to init.d scripts based on systemd and the possibility of making something like systemd configuration be the source for generating sysv scripts. Do we have anything that's usable for this now? I've got some rather shoddy init.d scripts

Bug#639956: ITP: xc3sprog -- JTAG flashing tool for FPGAs, CPLDs, and EEPROMs

2011-08-31 Thread Uwe Hermann
Package: wnpp Severity: wishlist Owner: Uwe Hermann * Package name: xc3sprog Version : r648 Upstream Author : Andrew Rogers, Uwe Bonnes, others * URL : http://sourceforge.net/projects/xc3sprog/ * License : GPL Programming Lang: C++ Description : JTAG fl

ArtSkills Web Link Request

2011-08-31 Thread Craig Kuehner
Hello, we have visited http://lists.debian.org/debian-user/2000/06/msg00062.html and think it is terrific. We believe your audience may benefit from knowing about us and our free online poster making resources. Who are we? We are ArtSkills, and we know everything about posters and poster making

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Kurt Roeckx
On Wed, Aug 31, 2011 at 02:42:41PM +0200, Lucas Nussbaum wrote: > On 31/08/11 at 12:58 +0100, Ben Hutchings wrote: > > On Wed, 2011-08-31 at 11:57 +0200, Lucas Nussbaum wrote: > > [...] > > > But a different thread library that has clear POSIX compliance bugs[*] > > > is the kind of things that mak

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Bernd Zeimetz
On 08/31/2011 01:45 PM, Charles Plessy wrote: > Le Wed, Aug 31, 2011 at 11:35:59AM +0200, Andreas Barth a écrit : >> * Lucas Nussbaum (lu...@lucas-nussbaum.net) [110831 10:56]: >>> Also, in the case of architectures targetted at embedded systems (I'm >>> thinking about mips and mipsel), what is imp

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Kurt Roeckx
On Tue, Aug 30, 2011 at 11:05:03AM +0200, Bernhard R. Link wrote: > > (And try to imagine how hard it would have been to introduce amd64 > if alpha had not elliminated in many years work most of the subtle > 64 bit bugs found in most software, I doubt porters alone could have > completed this in t

Re: simple Debian package information in the wiki

2011-08-31 Thread Henri Le Foll
First, to close the subject on debian-devel, I have sent this mail also to debian-mentors. please reply to debian-mentors. after this mail http://lists.debian.org/debian-devel/2011/08/msg00742.html I have put on the wiki some of my documentation about packaging. After some replies on debian-devel

Re: Maintainers, porters, and burden of porting [and 1 more messages]

2011-08-31 Thread Kurt Roeckx
On Wed, Aug 31, 2011 at 02:52:53PM +0100, Ian Jackson wrote: > Let me make an alternative proposal: > > * The root cause bug in the BTS would be given a special tag >("arch-blocker:" or something). I will call such a bug which >is open and has existed in this state for 30 days a "ripe ar

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Kurt Roeckx
On Wed, Aug 31, 2011 at 04:30:56AM +, Felipe Sateler wrote: > > I think some clarification needs to be done for these types of errors. I > sometimes get a (serious) bug reported against one of my packages because: > > 1. python errored out with a glibc-detected error > 2. gcc broke in some w

Re: Re: ifupdown package interfaces include function

2011-08-31 Thread Roger Leigh
On Wed, Aug 31, 2011 at 04:21:34PM +0200, Fabian Greffrath wrote: > >ifupdown 0.7~alpha5 was uploaded to unstable rather than experimental by > >mistake. Since version numbers aren't allowed to go backwards, we now > >have 0.7~alpha5+really0.6.15 in unstable, but for the purposes of > > Don't we

Re: simple Debian package information in the wiki

2011-08-31 Thread Stefano Zacchiroli
On Wed, Aug 31, 2011 at 05:03:25PM +0200, Gergely Nagy wrote: > I maintain my view that to learn packaging, the best way to do that is > to start from scratch I agree, but the request posted to this list was not about *learning* packaging. Rather, it reads: > I would like to make very simple Debi

Re: simple Debian package information in the wiki

2011-08-31 Thread Matt Zagrabelny
On Wed, Aug 31, 2011 at 10:03 AM, Gergely Nagy wrote: > Henri Le Foll writes: > >> http://wiki.debian.org/Packaging/Minimal (for empty packages) >> http://wiki.debian.org/Packaging/Trivial (for a pdf file) >> >> http://wiki.debian.org/Packaging >> >> I am interested to have feed back on it > > I

Re: Re: ifupdown package interfaces include function

2011-08-31 Thread Colin Watson
On Wed, Aug 31, 2011 at 04:21:34PM +0200, Fabian Greffrath wrote: > Don't we have epochs for this? I know they are annoying and should > be avoided, but they are still a blessing compared to the current > confused versioning scheme. Epochs are for when your entire version numbering scheme permanen

Re: simple Debian package information in the wiki

2011-08-31 Thread Ian Jackson
Henri Le Foll writes ("simple Debian package information in the wiki"): > http://wiki.debian.org/Packaging/Trivial (for a pdf file) If nothing else, this advises DFSG-violation, since a pdf is practically never its own source code. I agree with many of the criticisms from others, too. Ian. --

Re: simple Debian package information in the wiki

2011-08-31 Thread Gergely Nagy
Henri Le Foll writes: > http://wiki.debian.org/Packaging/Minimal (for empty packages) > http://wiki.debian.org/Packaging/Trivial (for a pdf file) > > http://wiki.debian.org/Packaging > > I am interested to have feed back on it I maintain my view that to learn packaging, the best way to do that i

Re: Re: ifupdown package interfaces include function

2011-08-31 Thread Samuel Thibault
Fabian Greffrath, le Wed 31 Aug 2011 16:21:34 +0200, a écrit : > >ifupdown 0.7~alpha5 was uploaded to unstable rather than experimental by > >mistake. Since version numbers aren't allowed to go backwards, we now > >have 0.7~alpha5+really0.6.15 in unstable, but for the purposes of > > Don't we hav

Re: Re: ifupdown package interfaces include function

2011-08-31 Thread Fabian Greffrath
ifupdown 0.7~alpha5 was uploaded to unstable rather than experimental by mistake. Since version numbers aren't allowed to go backwards, we now have 0.7~alpha5+really0.6.15 in unstable, but for the purposes of Don't we have epochs for this? I know they are annoying and should be avoided, but th

Re: simple Debian package information in the wiki

2011-08-31 Thread Josue Abarca
On Wed, Aug 31, 2011 at 02:18:41PM +0200, Henri Le Foll wrote: > Hi Stéphane, > > I have just created some pages on the wiki : > > http://wiki.debian.org/Packaging/Minimal (for empty packages) > http://wiki.debian.org/Packaging/Trivial (for a pdf file) > > http://wiki.debian.org/Packaging > > I

Re: simple Debian package information in the wiki

2011-08-31 Thread Игорь Пашев
I think dh_make is not so good for *simple* package, and is not good at all :-) 2011/8/31 Henri Le Foll > Hi Stéphane, > > I have just created some pages on the wiki : > > http://wiki.debian.org/Packaging/Minimal (for empty packages) > http://wiki.debian.org/Packaging/Trivial (for a pdf file) >

simple Debian package information in the wiki

2011-08-31 Thread Henri Le Foll
Hi Stéphane, I have just created some pages on the wiki : http://wiki.debian.org/Packaging/Minimal (for empty packages) http://wiki.debian.org/Packaging/Trivial (for a pdf file) http://wiki.debian.org/Packaging I am interested to have feed back on it Thanks Henri Le Foll -- To UNSUBSCRIBE,

Re: Maintainers, porters, and burden of porting [and 1 more messages]

2011-08-31 Thread Ian Jackson
Lucas Nussbaum writes ("Maintainers, porters, and burden of porting"): > However, issues such as miscompilation or broken syscall or libc > semantics are largely undetected. To illustrate this, you can have a > look at #635126 (miscompilation on armel and sparc) and #639658 > (forks+threads fun on

Bug#639898: ITP: pxljr -- driver for HP's Color LaserJet 35xx/36xx color laser printers

2011-08-31 Thread Didier Raboud
Package: wnpp Severity: wishlist Owner: Didier Raboud -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package name: pxljr Version : 1.3 Upstream Author : Hin-Tak Leung URL : http://hp-pxl-jetready.sourceforge.net/ License : GPL-2+, LibJPEG Programming

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Philipp Kern
On 2011-08-31, Paul Wise wrote: > On Tue, Aug 30, 2011 at 10:34 AM, Lars Wirzenius wrote: >> But both are wrong, too: it's always the job of both. It's not supposed >> to be a struggle between maintainers and porters, but everyone in >> Debian against bugs and shortcomings of our system. Also, nei

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Lucas Nussbaum
On 31/08/11 at 12:58 +0100, Ben Hutchings wrote: > On Wed, 2011-08-31 at 11:57 +0200, Lucas Nussbaum wrote: > [...] > > But a different thread library that has clear POSIX compliance bugs[*] > > is the kind of things that make me fear that many more packages than we > > see currently are broken on

Re: ifupdown package interfaces include function

2011-08-31 Thread Colin Watson
On Wed, Aug 31, 2011 at 02:04:19PM +0200, Sébastien Riccio wrote: > I found this "bug" report that is talking exactly about what I'm > looking for and provides patches > If i'm right it seems it has been closed and merged in ifupdown-0.7~alpha4. [...] > The package version installed on my box is: >

Re: ifupdown package interfaces include function

2011-08-31 Thread Sébastien Riccio
On 31.08.2011 14:14, Gergely Nagy wrote: Sébastien Riccio writes: If i'm right it seems it has been closed and merged in ifupdown-0.7~alpha4. [...] The package version installed on my box is: ifupdown 0.7~alpha5+really0.6.15 Notice the +really0.6.15. Try with the ifu

Re: ifupdown package interfaces include function

2011-08-31 Thread Gergely Nagy
Sébastien Riccio writes: > If i'm right it seems it has been closed and merged in ifupdown-0.7~alpha4. [...] > The package version installed on my box is: > ifupdown 0.7~alpha5+really0.6.15 Notice the +really0.6.15. Try with the ifupdown from experimental, which IS 0.7~al

ifupdown package interfaces include function

2011-08-31 Thread Sébastien Riccio
Hi, While "trying" to port the Xen (xapi) network reconfiguration scripts to debian for the project "Kronos", I was looking if there was a way to use includes in the /etc/network/interfaces file, for example /etc/network/interfaces.d/* I found this "bug" report that is talking exactly about w

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Ben Hutchings
On Wed, 2011-08-31 at 11:57 +0200, Lucas Nussbaum wrote: [...] > But a different thread library that has clear POSIX compliance bugs[*] > is the kind of things that make me fear that many more packages than we > see currently are broken on kfreebsd. And I'm not sure that it's where > we want to spe

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Charles Plessy
Le Wed, Aug 31, 2011 at 11:35:59AM +0200, Andreas Barth a écrit : > * Lucas Nussbaum (lu...@lucas-nussbaum.net) [110831 10:56]: > > Also, in the case of architectures targetted at embedded systems (I'm > > thinking about mips and mipsel), what is important is that Debian > > infrastructure supports

Re: Dependencies of metapackages

2011-08-31 Thread Wolodja Wentland
On Tue, Aug 30, 2011 at 17:37 +0200, Yves-Alexis Perez wrote: > On mar., 2011-08-30 at 16:11 +0100, Wolodja Wentland wrote: > > > > I agree that a general change of all metapackages is probably not a good > > idea, > > but I think that changing the root-nodes of the metapackage tree (i.e. > > met

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Samuel Thibault
Lucas Nussbaum, le Wed 31 Aug 2011 12:25:24 +0200, a écrit : > So, it's a really interesting project, but not really a proof of > widespread kfreebsd usage in high-demand production environments like > you seem to imply ;) Well, I didn't want to imply anything at all, just that it was a decision t

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Lucas Nussbaum
On 31/08/11 at 12:03 +0200, Samuel Thibault wrote: > Andreas Barth, le Wed 31 Aug 2011 11:35:59 +0200, a écrit : > > I know people who put kbsd on edge firewalls because it's way easier > > for a standard linux / debian admin. > > We are considering this in our ISP, as well. Come on, Samuel. You

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Andreas Barth
* Lucas Nussbaum (lu...@lucas-nussbaum.net) [110831 12:07]: > On 31/08/11 at 11:40 +0200, Andreas Barth wrote: > > * Lucas Nussbaum (lu...@lucas-nussbaum.net) [110831 07:34]: > > > Being in the second set would be fine, and would not be a step towards > > > being thrown out of Debian. Maintainers s

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Paul Wise
On Tue, Aug 30, 2011 at 10:34 AM, Lars Wirzenius wrote: > But both are wrong, too: it's always the job of both. It's not supposed > to be a struggle between maintainers and porters, but everyone in > Debian against bugs and shortcomings of our system. Also, neither group > is homogenous, and it's

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Lucas Nussbaum
On 31/08/11 at 11:40 +0200, Andreas Barth wrote: > * Lucas Nussbaum (lu...@lucas-nussbaum.net) [110831 07:34]: > > Being in the second set would be fine, and would not be a step towards > > being thrown out of Debian. Maintainers should still help porters get > > their packages ported, etc. But it

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Lucas Nussbaum
On 31/08/11 at 11:24 +0200, Cyril Brulebois wrote: > Lucas Nussbaum (31/08/2011): > > hurd-i386, kfreebsd-i386 and kfreebsd-amd64 are probably too > > experimental to be used on production systems. For kfreebsd, my main > > problem (with my Ruby hat) is the linuxthreads-based thread library, but >

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Samuel Thibault
Andreas Barth, le Wed 31 Aug 2011 11:35:59 +0200, a écrit : > I know people who put kbsd on edge firewalls because it's way easier > for a standard linux / debian admin. We are considering this in our ISP, as well. Samuel -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Bernd Zeimetz
On 08/31/2011 11:35 AM, Andreas Barth wrote: > * Lucas Nussbaum (lu...@lucas-nussbaum.net) [110831 10:56]: >> Also, in the case of architectures targetted at embedded systems (I'm >> thinking about mips and mipsel), what is important is that Debian >> infrastructure supports the development of thos

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Andreas Barth
* Lucas Nussbaum (lu...@lucas-nussbaum.net) [110831 07:34]: > Regarding architectures, we made releases with a semi-official status on > two occasions at least (etch-m68k and kfreebsd in squeeze). I hope you see the difference between etch-m68k and kbsd. Kbsd is "too new", whereas etch-m68k was (

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Andreas Barth
* Lucas Nussbaum (lu...@lucas-nussbaum.net) [110831 10:56]: > Also, in the case of architectures targetted at embedded systems (I'm > thinking about mips and mipsel), what is important is that Debian > infrastructure supports the development of those architectures, but I > don't think that there's

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Cyril Brulebois
Lucas Nussbaum (31/08/2011): > hurd-i386, kfreebsd-i386 and kfreebsd-amd64 are probably too > experimental to be used on production systems. For kfreebsd, my main > problem (with my Ruby hat) is the linuxthreads-based thread library, but > there might be other problems. http://lists.debian.org/87

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Bernhard R. Link
* Kurt Roeckx [110831 00:01]: > On Mon, Aug 29, 2011 at 01:06:15PM +0200, Lucas Nussbaum wrote: > I think to have a useful discussion we need to start with the > different kind of failures we can actually see that are arch > dependend. Some of those shows up on only 1 or 2 arches, some > show up

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Bernhard R. Link
* Lucas Nussbaum [110831 10:56]: > Note that I'm not saying that we should get rid of them. Only that we > should move them out of the "critical path". If there are active buildd > admins, I don't see why they couldn't continue to use Debian > infrastructure. And let the software in Debian rot mo

Re: Where can I found resource to make very simple Debian package like doc-linux-html… ?

2011-08-31 Thread Andrey Rahmatullin
On Wed, Aug 31, 2011 at 09:54:28AM +0200, Stéphane Klein wrote: > Hi, > > I would like to make very simple Debian package to install very > simple file on my system, only static file, like documentation. The only difference between a project with static files and a project with software is usually

Re: Where can I found resource to make very simple Debian package like doc-linux-html… ?

2011-08-31 Thread Arno Töll
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Stéphane, On 31.08.2011 09:54, Stéphane Klein wrote: > Where can I found some resources (url) to make this kind of package ? > I've found only resource about build package with compiled project… I've > already make a package for autotools… project.

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Lucas Nussbaum
On 31/08/11 at 10:37 +0200, Bernd Zeimetz wrote: > On 08/31/2011 07:34 AM, Lucas Nussbaum wrote: > > I've always wondered what was the point of having some architectures > > part of stable releases as official architectures. Sure, they are very > > useful as experimental architectures, and very fun

Where can I found resource to make very simple Debian package like doc-linux-html… ?

2011-08-31 Thread Stéphane Klein
Hi, I would like to make very simple Debian package to install very simple file on my system, only static file, like documentation. I've look "doc-linux-html" package to understand how it's builded. Where can I found some resources (url) to make this kind of package ? I've found only resource

Re: Maintainers, porters, and burden of porting

2011-08-31 Thread Bernd Zeimetz
On 08/31/2011 07:34 AM, Lucas Nussbaum wrote: > I've always wondered what was the point of having some architectures > part of stable releases as official architectures. Sure, they are very > useful as experimental architectures, and very fun to work on, but it's > unlikely that people will use the

Bug#639868: ITP: chado -- Chado is a relational database schema that underlies many GMOD installations.

2011-08-31 Thread Olivier Sallou
Package: wnpp Severity: wishlist Owner: Olivier Sallou * Package name: chado Version : 1.11 Upstream Author : GMOD * URL : http://gmod.org/wiki/Chado_-_Getting_Started * License : Artistic License 2.0 Programming Lang: Perl,SQL Description : Chado is a