Hendrik Sattler wrote:
> Am Montag, 29. Mai 2006 21:16 schrieb Thomas Viehmann:
>> Hendrik Sattler wrote:
>>> No, but you could manually set all stuff in Depends to the needed
>>> versions. That would also work for the buildds, I guess.
>> And break at the next opportunity (binNMU, recompile, updat
Tyler MacDonald wrote:
WTF? In Oregon, if you have a driver's license, you cannot get an ID card.
If you have an ID card, you have to surrender it to get a driver's license.
You're only legally allowed one ID.
Weird!
Not really, same rules apply in Virginia, AFAIK.
You can still
Kevin B. McCarty wrote:
Come to think of it, [pgp encrypting each message] isn't a bad idea. Is it
feasible for this to
be done transparently? Mailing list admins, any comments?
I suspect that the end result of this would be more people keeping their
GPG keys unencrypted on Internet-access
> * python-imaging
> (easy pickings)
as former maintainer of this package and having used that as an
example package, I'd like to maintain this one again.
Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
internet marketers,
Do you dream about retiring early?
We have the leads, business, automated systems, and product to help you do it.
We charge nothing to send you more information.
Our team has over 8 years of proven success; we will share all.
Get more now::
http://windows.topincome-superst
On (29/05/06 21:29), [EMAIL PROTECTED] wrote:
> Hi,
>
> My inability to find enough time to focus on package maintainance
> has been *way* too persistent. I therefore need to give up my packages
> for adoption, for the time being.
That's a shame.
> * gnutls, gcrypt, libtasn1, libksba
> (securi
Em Seg, 2006-05-29 às 23:59 +0100, Steve Kemp escreveu:
> On Mon, May 29, 2006 at 07:53:02PM -0300, Daniel Ruoso wrote:
> > In fact, I want it to work as a native debian system. This way,
> > buildroot causes a lot of problems
> Isn't this what 'apt-build' can be used for?
> That allows you to reb
On Mon, May 29, 2006 at 07:53:02PM -0300, Daniel Ruoso wrote:
> In fact, I want it to work as a native debian system. This way,
> buildroot causes a lot of problems
Isn't this what 'apt-build' can be used for?
http://julien.danjou.info/article-apt-build.html
That allows you to rebuild
Em Seg, 2006-05-29 às 22:08 +0100, Chris Boot escreveu:
> SLIND sounds interesting indeed, I've been using a buildroot-built
> system for mine so it was difficult getting dpkg built in the first
> place, but I've got it mostly all going. All the arch-independent
> packages help a lot too.
In
On Mon, May 29, 2006 at 09:47:53PM +0200, Goswin von Brederlow wrote:
> Or just dump all packages into the buildds queue file (as
That would be ~buildd/build/REDO
> package_version, one per line) and start it.
That would be
package_version distribution
instead, as in
nbd_1:2.8.4-2 unstable
W
Am Montag, 29. Mai 2006 21:16 schrieb Thomas Viehmann:
> Hendrik Sattler wrote:
> > No, but you could manually set all stuff in Depends to the needed
> > versions. That would also work for the buildds, I guess.
>
> And break at the next opportunity (binNMU, recompile, update in a
> hurry...).
If h
On 29 May 2006, at 18:32, Daniel Ruoso wrote:
Em Seg, 2006-05-29 às 13:49 +0100, Chris Boot escreveu:
I'm starting work again on a thinned-down version of Debian I call
PicoDebian.
The idea of this new version is to replace glibc with uClibc, and
generally slim
down various packages to fit
* () wrote:
> Hi,
>
> My inability to find enough time to focus on package maintainance
> has been *way* too persistent. I therefore need to give up my packages
> for adoption, for the time being.
>
> I am sorry (and not happy with myself) that I've been procrastinating
> about this for too long
On Mon, May 29, 2006 at 09:29:34PM +0200, wrote:
> * festival, speech-tools
> (some clean-up work, new major upstream release pending)
[..]
> * gnupg2
> (some clean-up work)
I'd be interested in taking these three, especially gnupg2 as I'm using
it on a daily basis.
Thanks,
Franz
--
Franz
also sprach <> [2006.05.29.2129 +0200]:
> * python-docutils
> (easy pickings)
I'd like to take that on. I am already co-maintainer. Other
co-maintainers welcome.
--
Please do not send copies of list mail to me; I read the list!
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' :prou
martin f krafft <[EMAIL PROTECTED]> wrote:
> also sprach Thomas Viehmann <[EMAIL PROTECTED]> [2006.05.29.2122 +0200]:
>> I think the usual way is to provide the dummy binary package
>> immediately from the new source package and file a bug for removal
>> of the old source package.
>
> Sounds like
martin f krafft <[EMAIL PROTECTED]> writes:
> also sprach Thomas Viehmann <[EMAIL PROTECTED]> [2006.05.29.2122 +0200]:
>> I think the usual way is to provide the dummy binary package
>> immediately from the new source package and file a bug for removal
>> of the old source package.
>
> Sounds like
Hendrik Sattler <[EMAIL PROTECTED]> writes:
> Am Montag, 29. Mai 2006 10:27 schrieb Frank Küster:
>> Would it be acceptable to build bacula (or any other package with that
>> problem) in an etch environment, or on sid with manually installed
>> libssl from etch, and upload that to unstable? Â Aft
Bastian Venthur <[EMAIL PROTECTED]> writes:
> Hi all,
>
> I want to rebuild the whole archive on my box but I don't really know
> where to start. I don't want to keep the resulting packages, I just want
> to seek FTBFSes.
>
> I've installed sbuild (do I really need it? Does pbuilder/cowbuilder
> s
Hi,
My inability to find enough time to focus on package maintainance
has been *way* too persistent. I therefore need to give up my packages
for adoption, for the time being.
I am sorry (and not happy with myself) that I've been procrastinating
about this for too long. This decision has not been
* Hendrik Sattler [Mon, 29 May 2006 20:58:19 +0200]:
> PS: I bravely accept some flames for this suggestion...
Sure, here, have some:
- http://lists.debian.org/debian-devel/2006/05/msg01393.html
- http://lists.debian.org/debian-devel/2006/05/msg00752.html
- http://lists.debian.org/debian-l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
martin f krafft wrote:
> also sprach Andreas Fester <[EMAIL PROTECTED]> [2006.05.29.2114 +0200]:
>> Replaces: oldPackage
>> Conflicts: oldPackage (<< firstVersionOfNewPackage)
>
> Also: Provides: oldPackage, so that it can still satisfy
> (non-version
Javier Fernández-Sanguino Peña wrote:
> Regardless of this, I think it would be nice to have a document (wikipedia
> article?) listing official documents of countries all over the world. KSP
> attendants need not base their decissions on this, but could be useful
> as background information.
>
> I
martin f krafft <[EMAIL PROTECTED]> writes:
> also sprach Thomas Viehmann <[EMAIL PROTECTED]> [2006.05.29.2122 +0200]:
>> I think the usual way is to provide the dummy binary package
>> immediately from the new source package and file a bug for removal
>> of the old source package.
> Sounds like a
On Mon, May 29, 2006 at 08:58:19PM +0200, Hendrik Sattler wrote:
> Am Montag, 29. Mai 2006 10:27 schrieb Frank Küster:
> > Would it be acceptable to build bacula (or any other package with that
> > problem) in an etch environment, or on sid with manually installed
> > libssl from etch, and upload t
On Mon, May 29, 2006 at 09:26:41PM +0200, martin f krafft <[EMAIL PROTECTED]>
wrote:
> also sprach Thomas Viehmann <[EMAIL PROTECTED]> [2006.05.29.2122 +0200]:
> > I think the usual way is to provide the dummy binary package
> > immediately from the new source package and file a bug for removal
>
* martin f krafft [Mon, 29 May 2006 21:26:41 +0200]:
> I doubt you can upload a source package that generates the same
> binary package as another source package.
You definitely can, and TTBOMK it does not even need NEW if the source
package that starts shipping it already existed.
--
Adeodato
On Sun, May 28, 2006 at 11:40:46PM +0200, Javier Fernández-Sanguino Peña wrote:
> (...) they *have* to provide you with a passport. Not because it is
> a requirement, but because you have the *right* to travel abroad (at
> least it is in Spain)
That's a human right, as defined by the Universal De
also sprach Thomas Viehmann <[EMAIL PROTECTED]> [2006.05.29.2122 +0200]:
> I think the usual way is to provide the dummy binary package
> immediately from the new source package and file a bug for removal
> of the old source package.
Sounds like a clean approach, but is there a clean transition?
I
also sprach Andreas Fester <[EMAIL PROTECTED]> [2006.05.29.2114 +0200]:
> Replaces: oldPackage
> Conflicts: oldPackage (<< firstVersionOfNewPackage)
Also: Provides: oldPackage, so that it can still satisfy
(non-versioned) dependencies.
But yeah, seems like the right way to do things.
--
Please
Andreas Fester wrote:
> Is this the correct approach? Anything I missed?
I think the usual way is to provide the dummy binary package immediately
from the new source package and file a bug for removal of the old source
package.
Kind regards
T.
--
Thomas Viehmann, http://thomas.viehmann.net/
-
Hendrik Sattler wrote:
> Am Montag, 29. Mai 2006 10:27 schrieb Frank Küster:
>> Would it be acceptable to build bacula (or any other package with that
>> problem) in an etch environment, or on sid with manually installed
>> libssl from etch, and upload that to unstable? After checking that it
>> w
Hello, On 5/26/06, David Moreno Garza <[EMAIL PROTECTED]> wrote:
You _usually_ don't get your passport stamped? Really? In recent flights?I have never entered Mexico back without the Immigration seal.Yeah, depends on the mood of the one attending you.
True! And even by plane! Which I found extreme
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone,
this has already been discusses some times, but
since this is a new situation for me I want to be
sure that it is still true and that I handle it properly :-)
Problem:
Upstream application (non-library) has changed its name.
I want to r
Am Montag, 29. Mai 2006 10:27 schrieb Frank Küster:
> Would it be acceptable to build bacula (or any other package with that
> problem) in an etch environment, or on sid with manually installed
> libssl from etch, and upload that to unstable? After checking that it
> works in unstable, of course.
Hi all,
I want to rebuild the whole archive on my box but I don't really know
where to start. I don't want to keep the resulting packages, I just want
to seek FTBFSes.
I've installed sbuild (do I really need it? Does pbuilder/cowbuilder
suffice?) and followed the instructions of the manpage to se
Em Seg, 2006-05-29 às 13:49 +0100, Chris Boot escreveu:
> I'm starting work again on a thinned-down version of Debian I call
> PicoDebian.
> The idea of this new version is to replace glibc with uClibc, and generally
> slim
> down various packages to fit nicely in confined environments.
This n
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Sun, May 28, 2006 at 08:57:55PM -0700, Thomas Bushnell BSG wrote:
>
>> > If I were to crack a key signing party, using Bubba's travel
>> > documents, I too would swear up and down the street that he indeed
>> > correctly and diligently veri
Stefano Zacchiroli wrote:
> On Sun, May 28, 2006 at 11:42:16PM +0200, Bartosz Fenski aka fEnIo wrote:
>
>> I think it's debconf time and everything is slower, but will be as
>> usual when it's end and everyone came back to his/her normal work.
>>
>
> The point of the first mail was exactly
Javier Fernández-Sanguino Peña dijo [Sun, May 28, 2006 at 11:40:46PM +0200]:
> > > For me, yes, some questions asked, some delays involved, but no
> > > detailed background checks. I'm sure neither the FBI or the CIA (or,
> > > as for Mexican authorities, CISEN or PGR) were involved.
> >
> >
General info
Subscription/unsubscription/info requests should always be sent to
the -request address of a mailing list.
If a mailing list is called for example "[EMAIL PROTECTED]", then
the -request address can be inferred from this to b
General info
Subscription/unsubscription/info requests should always be sent to
the -request address of a mailing list.
If a mailing list is called for example "[EMAIL PROTECTED]", then
the -request address can be inferred from this to b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, 27 May 2006 16:21:22 -0700
Paul Johnson <[EMAIL PROTECTED]> wrote:
> On Saturday 27 May 2006 16:12, Ron Johnson wrote:
> > Paul Johnson wrote:
> > > On Saturday 27 May 2006 14:12, Steinar H. Gunderson wrote:
> > >> On Sat, May 27, 2006 at 01:5
Hi all,
I'm starting work again on a thinned-down version of Debian I call PicoDebian.
The idea of this new version is to replace glibc with uClibc, and generally slim
down various packages to fit nicely in confined environments.
I've managed to build several of the base-system packages alrea
On Sun, May 28, 2006 at 10:37:39PM -0500, Manoj Srivastava wrote:
> On 27 May 2006, martin f. krafft spake thusly:
> > From within the project, what matters is that everything you do
> > within the project can be attributed to one and the same person: the
> > same person that went through our NM pr
[EMAIL PROTECTED] (Marco d'Itri) wrote:
> On May 29, Frank Küster <[EMAIL PROTECTED]> wrote:
>
>> - Setups without an existing $HOME directory can exist, and package
>> building must work there, correct?
> I'd say that packages being built should not create files outside of the
> build directory
On Mon, May 29, 2006 at 03:49:28PM +1000, Aníbal Monsalve Salazar wrote:
> On Sun, May 28, 2006 at 06:40:28PM -0500, Andrew McMillan wrote:
> >On Sun, 2006-05-28 at 04:54 -0700, Steve Langasek wrote:
> >>On Sat, May 27, 2006 at 04:47:20PM -0500, martin f krafft wrote:
> >>
> >>>I imagine an improve
On Sun, May 28, 2006 at 11:12:16PM -0500, Manoj Srivastava wrote:
> So, once someone acts in bad faith, I can't trust anything
> else they say: How do I know it is not a hoax within a hoax to see
> how gullible people are, to accept that the papers presented were not
> faked, or outright
On May 29, Frank Küster <[EMAIL PROTECTED]> wrote:
> - Setups without an existing $HOME directory can exist, and package
> building must work there, correct?
I'd say that packages being built should not create files outside of the
build directory. But creating ~ is simple enough that I think it'
Okay, let's take this to -devel; I hope we'll get a bit more of answers
instead of just new questions there...
We are thinking about ways to make TeX font caching safer than it
currently is, without breaking buildd's or unusual setups. The current
idea is to cache the font data in each user's hom
Debian Bug Tracking System writes:
> Le Lun 29 Mai 2006 03:40, Matthias Klose a =E9crit :
>
> > the only thing that is correct. is the syntax. everything else is
> > wrong. the messages should have been generated for gcc-snapshot (if
> > at all), but not for 4.1.
>
> debian bug http://bugs.debian
On Mon, May 29, 2006 at 12:11:17PM +0200, Matthias Klose wrote:
> Debian Bug Tracking System writes:
> > Le Lun 29 Mai 2006 03:40, Matthias Klose a =E9crit :
> >
> > > the only thing that is correct. is the syntax. everything else is
> > > wrong. the messages should have been generated for gcc-sna
* Mark Brown:
> On Mon, May 29, 2006 at 10:27:45AM +0200, Frank K?ster wrote:
>
>> Would it be acceptable to build bacula (or any other package with that
>> problem) in an etch environment, or on sid with manually installed
>> libssl from etch, and upload that to unstable? After checking that it
On Mon, May 29, 2006 at 10:27:45AM +0200, Frank K?ster wrote:
> Would it be acceptable to build bacula (or any other package with that
> problem) in an etch environment, or on sid with manually installed
> libssl from etch, and upload that to unstable? After checking that it
> works in unstable,
On Mon, 29 May 2006 10:27:45 +0200, Frank Küster <[EMAIL PROTECTED]>
wrote:
>Would it be acceptable to build bacula (or any other package with that
>problem) in an etch environment, or on sid with manually installed
>libssl from etch, and upload that to unstable?
No, that won't fix the problem for
Sorry for the late message to this thread.
* Gabor Gombas wrote:
> On Sat, May 20, 2006 at 01:58:14AM +0200, Adam Borowski wrote:
> > Thus, it's bash's start-up which is the slow part, in the terms of
> > actual speed, bash is not that far behind.
>
> It would be interesting to compare something
#include
* Jörg Sommer [Sat, May 27 2006, 10:59:39PM]:
> > No, they don't. At least my packages call it only if `uname -r` ==
> > target version. When you drop the depmod run, and someone installs a new
> > kernel together with accompanying module packages and only THEN reboots,
> > the modules.d
Andreas Metzler <[EMAIL PROTECTED]> wrote:
>> Hmm. But openssl is in testing already, and bacula doesn't build-dep
>> on a newer version. Why does it matter?
>
> The *binary* packages require a newer version of openssl, they would
> be uninstallable in testing.
>
> http://packages.debian.org/uns
Scripsit Manoj Srivastava <[EMAIL PROTECTED]>
> I see you have never been in a large key signing party. There
> is a certain expectation of trust, since no one can actrually detect
> delibrate forgeries.
If a key-signing method needs any particularly trustworthy behavior
from the peopl
Your message dated Mon, 29 May 2006 09:01:54 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#369257: remote bug tracking system doesn't look at versions
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Le Lun 29 Mai 2006 07:50, Thomas Bushnell BSG a écrit :
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > Um... usertags have user-defined semantics. How can you claim that
> > the usertags being set are wrong?
>
> As I understand it, the complaint is that bts-link is changing user
> tags set by t
Le Lun 29 Mai 2006 03:40, Matthias Klose a écrit :
> the only thing that is correct. is the syntax. everything else is
> wrong. the messages should have been generated for gcc-snapshot (if
> at all), but not for 4.1.
debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=356569
is about gcc-
Package: wnpp
Severity: wishlist
Owner: Vincent Danjean <[EMAIL PROTECTED]>
* Package name: phpmybibli
Version : 2.1.24
Upstream Author : [EMAIL PROTECTED]
* URL : http://www.pizz.net/index_logiciel.php
* License : CeCILL
Programming Lang: php
Description
63 matches
Mail list logo
