On Fri, 2007-11-23 at 10:39 +0100, Raphael Hertzog wrote:
> Hello,
Hello,
> as announced in
> http://lists.debian.org/debian-devel-announce/2007/09/msg4.html the
> new dpkg-shlibdeps is stricter in what it accepts and will fail when it
> can't find dependency information for a library that is
On Sat, Nov 24, 2007 at 02:30:17AM +0100, Ondrej Certik wrote:
> On Nov 24, 2007 1:17 AM, Pierre Habouzit <[EMAIL PROTECTED]> wrote:
> > On Sat, Nov 24, 2007 at 12:01:33AM +, Paul Wise wrote:
> > > On Nov 24, 2007 6:14 AM, Alex Samad <[EMAIL PROTECTED]> wrote:
> > > > trying to build a i386 pa
On Nov 24, 2007 1:17 AM, Pierre Habouzit <[EMAIL PROTECTED]> wrote:
> On Sat, Nov 24, 2007 at 12:01:33AM +, Paul Wise wrote:
> > On Nov 24, 2007 6:14 AM, Alex Samad <[EMAIL PROTECTED]> wrote:
> >
> > > trying to build a i386 package on a amd64 machine and i keep getting
> >
> > Are you building
On Sat, Nov 24, 2007 at 12:01:33AM +, Paul Wise wrote:
> On Nov 24, 2007 6:14 AM, Alex Samad <[EMAIL PROTECTED]> wrote:
>
> > trying to build a i386 package on a amd64 machine and i keep getting
>
> Are you building in an i386 chroot? If not, try that. Adding
> "--debootstrapopts --arch --deb
On Nov 24, 2007 6:14 AM, Alex Samad <[EMAIL PROTECTED]> wrote:
> trying to build a i386 package on a amd64 machine and i keep getting
Are you building in an i386 chroot? If not, try that. Adding
"--debootstrapopts --arch --debootstrapopts i386" to the
pbuilder/cowbuilder create command line shoul
On Fri, 23 Nov 2007, Luk Claes wrote:
> Nowadays there are better alternatives to uploading to unstable for
> archive wide testing IMHO. Uploading to experimental is a good thing to
> have some initial testing on many architectures, though I would go for a
> rebuild of the whole archive for testing
On Fri, Nov 23, 2007 at 09:49:10PM +, Luk Claes wrote:
> Raphael Hertzog wrote:
> > On Fri, 23 Nov 2007, Sune Vuorela wrote:
> >> On 2007-11-23, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> >>> Well, the d-d-a mail included a list of affected packages. So we had a
> >>> clue on how many package
> Ivan Shmakov <[EMAIL PROTECTED]> writes:
> David Weinehall <[EMAIL PROTECTED]> writes:
>>> A helper script, `lintian-man', could be introduced to hide all the
>>> hackery, and to provide a way for the developer to reproduce the
>>> problem. Then, Tag: may be changed to, e. g.,
>>> `
Raphael Hertzog wrote:
> On Fri, 23 Nov 2007, Sune Vuorela wrote:
>> On 2007-11-23, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
>>> Well, the d-d-a mail included a list of affected packages. So we had a
>>> clue on how many packages are affected. The list has probably evolved
>>> since september but
* Henrique de Moraes Holschuh:
> On Fri, 23 Nov 2007, Florian Weimer wrote:
>> Personally, what made me stick to Exim so far is the ability to
>> configure retry behavior on a per-domain basis. One of my mail servers
>
> Postfix does that too. You direct the domains to a different transport, and
On Fri, Nov 23, 2007 at 10:46:14AM +0100, Luca Capello wrote:
> Hi Alex!
>
> On Thu, 22 Nov 2007 22:20:12 +0100, Alex Samad wrote:
> > I am in the process of rebuilding one of my servers and I thought hey
> > why not build a package, that links all the other packages I need, and
> > the correspond
On Fri, 23 Nov 2007, Florian Weimer wrote:
> Personally, what made me stick to Exim so far is the ability to
> configure retry behavior on a per-domain basis. One of my mail servers
Postfix does that too. You direct the domains to a different transport, and
setup that transport with whichever pa
On Fri, Nov 23, 2007 at 07:55:00AM +0100, Andreas Tille wrote:
> On Fri, 23 Nov 2007, Alex Samad wrote:
>
>>> Yes, I'm doing this for years. I ended up with binary packages
>>> andreas-base, andreas-nox, andreas-x and andreas-laptop on my
>>> local mirror and these packages will be installed on ne
Hi
trying to build a i386 package on a amd64 machine and i keep getting
dpkg-gencontrol: error: current host architecture 'amd64' does not appear in
package's architecture list (i386)
I am using debhelper to build the packages and I have tried dh_gencontrol --
-VArch=i386
but doesn't seem to b
> Loïc Minier <[EMAIL PROTECTED]> writes:
>> I vaguely recall seeing a recommendation for library packages for a
>> particular language to follow libFOO-BAR naming convention in
>> Debian, where FOO is the name of a library, and BAR is an arbitrary
>> common suffix (thus, liberror-perl, or
Package: wnpp
Severity: wishlist
Owner: Rene Mayorga <[EMAIL PROTECTED]>
* Package name: libproc-fork-perl
Version : 0.4
Upstream Author : Aristotle Pagaltzis <[EMAIL PROTECTED]>
* URL : http://search.cpan.org/dist/Proc-Fork/
* License : GPL/Artistic
Programmi
Package: wnpp
Severity: wishlist
Owner: David Bremner <[EMAIL PROTECTED]>
Package name: bibutils
Version : 3.39
Upstream Author : Chris Putnam <[EMAIL PROTECTED]>
URL :
http://www.scripps.edu/~cdputnam/software/bibutils/bibutils.html
Programming Lang: C
Licens
Hello,
> I vaguely recall seeing a recommendation for library packages
> for a particular language to follow libFOO-BAR naming convention
> in Debian, where FOO is the name of a library, and BAR is an
> arbitrary common suffix (thus, liberror-perl, or
> libsqlite-oca
Hello,
> I vaguely recall seeing a recommendation for library packages
> for a particular language to follow libFOO-BAR naming convention
> in Debian, where FOO is the name of a library, and BAR is an
> arbitrary common suffix (thus, liberror-perl, or
> libsqlite-ocam
On Fri, Nov 23, 2007, Ivan Shmakov wrote:
> I vaguely recall seeing a recommendation for library packages
> for a particular language to follow libFOO-BAR naming convention
> in Debian, where FOO is the name of a library, and BAR is an
> arbitrary common suffix (thus, liberr
Hi Ivan,
* Ivan Shmakov <[EMAIL PROTECTED]> [2007-11-23 14:57]:
> I vaguely recall seeing a recommendation for library packages
> for a particular language to follow libFOO-BAR naming convention
> in Debian, where FOO is the name of a library, and BAR is an
> arbitrary commo
On Fri, Nov 23, 2007 at 01:40:39PM +, Raphael Hertzog wrote:
> I'd rather be more strict and relax the rules as we identify cases where I
> have been too strict, than let people upload broken .debs during weeks and
> later discover that we have to scan the full archive to rebuild
> a bunch of
I vaguely recall seeing a recommendation for library packages
for a particular language to follow libFOO-BAR naming convention
in Debian, where FOO is the name of a library, and BAR is an
arbitrary common suffix (thus, liberror-perl, or
libsqlite-ocaml.)
> David Weinehall <[EMAIL PROTECTED]> writes:
>> A helper script, `lintian-man', could be introduced to hide all
>> the hackery, and to provide a way for the developer to reproduce
>> the problem. Then, Tag: may be changed to, e. g.,
>> `manpage-has-messages-from-lintian-man'. (Or should
[ CCing #452511 as I provide an explanation of why we shouldn't change
back to --ignore-missing-info by default without careful consideration ]
On Fri, 23 Nov 2007, Pierre Habouzit wrote:
> Damn I wanted to answer to that, and forgot: I don't think anyone
> wants a revert. I'd expect you to make
Package: wnpp
Severity: wishlist
Owner: Guido Guenther <[EMAIL PROTECTED]>
* Package name: virt-viewer
Version : 0.0.2
* License : GPLv2
Programming Lang: C
Description : Displaying the graphical console of a virtual machine
The console is accessed using the VNC pro
Package: wnpp
Severity: wishlist
Owner: Guido Guenther <[EMAIL PROTECTED]>
* Package name: virtinst
* License : GPL
Programming Lang: Python
Description : Create and clone virtual machines
Create and clone virtual machines using libvirt.
http://git.debian.org/?p=users/agx/v
Package: wnpp
Severity: wishlist
Owner: Guido Guenther <[EMAIL PROTECTED]>
Description : A VNC viewer widget for GTK+
It is built using coroutines, allowing it to be completely asynchronous while
remaining single threaded. It supports RFB protocols 3.3 through 3.8 and the
VeNCrypt authent
On ven, nov 23, 2007 at 11:31:57 +, Raphael Hertzog wrote:
> But I'm just not willing to fully revert a decision
Damn I wanted to answer to that, and forgot: I don't think anyone
wants a revert. I'd expect you to make lower the dpkg-shlibdeps
expectations for a while, so that we can take ou
On 2007-11-23, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> they have some fixing to do (in particular when it looks like they don't
> really understand the issues at hand).
If this was targetted at me, then please explain me what I don't really
understand.
/Sune
--
To UNSUBSCRIBE, email to [E
On ven, nov 23, 2007 at 11:31:57 +, Raphael Hertzog wrote:
> (in particular when it looks like they don't really understand the
> issues at hand).
Please, this ad hominem isn't deserved, because the KDE team could
exactly answer the same to you. Mind you, but the huge workload you just
infli
On Fri, Nov 23, 2007 at 11:15:46AM +, Bernd Zeimetz wrote:
> Pierre Habouzit wrote:
>
> > But forcing every maintainer that probably had an agenda for their
> > package already, to comply to yours without even knowing what's coming
> > is at the very least tactless and disruptive.
>
> the n
On Fri, 23 Nov 2007, Sune Vuorela wrote:
> On 2007-11-23, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> > Well, the d-d-a mail included a list of affected packages. So we had a
> > clue on how many packages are affected. The list has probably evolved
> > since september but not by much.
>
> Except
Pierre Habouzit wrote:
> But forcing every maintainer that probably had an agenda for their
> package already, to comply to yours without even knowing what's coming
> is at the very least tactless and disruptive.
the new dpkg was in experimental for a long enough time, and this was
announced of
On Fri, 23 Nov 2007, Luca Capello wrote:
http://azure.humbug.org.au/~aj/blog/2007/11/14#2007-11-14-hacking-equivs
Well, if you really want a system to create your meta packages you could
either use equivs or cdd-dev. AJ is right here that you add a little bit
more complexity to the system, bu
On ven, nov 23, 2007 at 10:14:51 +, Raphael Hertzog wrote:
> On Fri, 23 Nov 2007, Pierre Habouzit wrote:
> > does your plan include having a version of the dpkg-shlibdeps that
> > works in "warning-mode" only so that we can have a more extensive idea
> > of how the things are going to be, bef
On 2007-11-23, Raphael Hertzog <[EMAIL PROTECTED]> wrote:
> Well, the d-d-a mail included a list of affected packages. So we had a
> clue on how many packages are affected. The list has probably evolved
> since september but not by much.
Except covering kde now. KDE didn't change that much since s
On Thu, 22 Nov 2007, Frank Küster wrote:
> Don Armstrong debian.org> writes:
> > Then why distribute the original PDFs at all in that case?
>
> Because the purpose of the document is to show the differences
> between several (free as well as non-free) fonts, and help the user
> make a choice.
So
On Fri, 23 Nov 2007, Pierre Habouzit wrote:
> does your plan include having a version of the dpkg-shlibdeps that
> works in "warning-mode" only so that we can have a more extensive idea
> of how the things are going to be, before it stops the development of
> the biggest and already hardest packa
On Fri, Nov 23, 2007 at 09:39:58AM +, Raphael Hertzog wrote:
> Hello,
>
> as announced in
> http://lists.debian.org/debian-devel-announce/2007/09/msg4.html the
> new dpkg-shlibdeps is stricter in what it accepts and will fail when it
> can't find dependency information for a library that i
Hi Alex!
On Thu, 22 Nov 2007 22:20:12 +0100, Alex Samad wrote:
> I am in the process of rebuilding one of my servers and I thought hey
> why not build a package, that links all the other packages I need, and
> the corresponding configuration files.
Not that I'm an expert on it, but it seems that
Hello,
as announced in
http://lists.debian.org/debian-devel-announce/2007/09/msg4.html the
new dpkg-shlibdeps is stricter in what it accepts and will fail when it
can't find dependency information for a library that is used by an
executable or a public library (a public library is defined as a
* Miles Bader:
> Postfix has a reputation for being faster and more secure than exim.
Nowadays, the Postfix code base is larger than the Exim code base.
> Why is it worth worrying about, though? Are the difference between exim
> and postfix really great enough to matter for typical use?!?
"/us
43 matches
Mail list logo
