Heya,
Roland Mas writes:
> Mike Hommey, 2011-05-04 07:57:47 +0200:
>> Add to that that allowing random people to upload packages to be built
>> on Debian build daemons is a recipe to have the buildds compromised.
> My initial idea about how one would go about implementing them
> involved very s
Heya,
Raphael Hertzog writes:
> I understand members of the release team feel particularly responsible to
> do various release-critical tasks that should have been done by the
> maintainers but haven't (for various reasons). And I guess that's the
> reason of your remark.
>
> But that's not scala
Hai!
Pierre Habouzit writes:
> On Sat, Apr 30, 2011 at 12:28:06PM +0200, Stefano Zacchiroli wrote:
>> Size is just one ingredient. There are plenty of other ways to diminish
>> barrier to deploy big changes in Debian: wider commit access rights,
>> larger VCS repositories, more liberal NMUs, etc.
Stefano Zacchiroli writes:
> On Sat, Apr 30, 2011 at 11:28:17AM +0200, Marc 'HE' Brockschmidt wrote:
>> In the last years, Debian hasn't been able to contribute any important
>> feature to the F/OSS distribution world - change (leading to both good
>> or
Heya,
Raphael Hertzog writes:
> On Sat, 30 Apr 2011, Marc 'HE' Brockschmidt wrote:
>> Raphael, it would be so great to reply to messages in single mails
>> instead of squeezing (are you release-themed, or what?) all of your
>> answers into one mail. I'm reall
Hi,
Lucas Nussbaum writes:
> Eh? How do you fix stuff in the next release if you don't make uploads?
> I'm not saying that the number of uploads should stay the same: it's
> normal to see it going down during freezes, since there are less things
> to change. However, if we think that DDs particip
Heya,
Raphael, it would be so great to reply to messages in single mails
instead of squeezing (are you release-themed, or what?) all of your
answers into one mail. I'm really tired of chasing a specific answer
From you through the whole thread.
Raphael Hertzog writes:
> But I don't plan to work
Julien Cristau writes:
> On Wed, Sep 22, 2010 at 16:24:44 +0200, Holger Levsen wrote:
>> On Mittwoch, 22. September 2010, Mike Hommey wrote:
>>> PS: for my personal needs, some way to get random packages autobuilt
>>> would already be helpful (call that ppa if you want).>>
>> I seem to recall, ft
Stanislav Maslovski writes:
> On Mon, Aug 09, 2010 at 05:22:27PM +0200, Sebastian Dröge wrote:
>> Backporting the lcdfilter patch to 1.8.10 might be a solution for
>> squeeze though. If someone wants to provide a patch that doesn't add any
>> new public API I'd be fine with applying it to the unst
Tiago Bortoletto Vaz writes:
> 1) consider that most of CPUs support this flag, so tell the reporter to
> compile the package by him/herself.
This is not acceptable and would make your package rc-buggy. Even though
it's called i386 and in fact only supports i486, we are not in a state
where we wa
Micah Anderson writes:
> Clint Adams writes:
>> [Adding and M-F-T-ing -project]
[...]
>> Were you there? Were Debian funds spend on this endeavor? What
>> happened there? Most importantly, why is it all so secretive?
>
> Did I miss a response to these questions? I'm interested to know the
> an
Stéphane Glondu writes:
> Raphael Hertzog a écrit :
>> I don't an exhaustive answer but here are some points:
>> 1/ you can't request bin-nmus of reverse-dependencies in experimental
>>(to verify that all packages build fine with the updated package, and
>>that's one of the main task in pr
Raphael Hertzog writes:
> To resolve the problems I suggest to serialize transitions in sid.
This was already discussed a few times.
> First the archive should block package uploads to sid that would be
> starting a new transition (defining this in more details is left for
> later).
No, this ca
Michael Hanke writes:
> since a while I try to figure out why a package is not being auto-built.
> I was suggested to contact the "team that runs the non-free
> autobuilders". However, I have trouble finding that team. Whom could I
> contact -- neither google nor the wiki seems to know about them.
Carlo Segre writes:
> On Mon, 22 Mar 2010, Marc 'HE' Brockschmidt wrote:
>> We are currently reworking the non-free support in the buildd
>> network. In the long term, we want to be able to build whitelisted
>> packages, and allow contrib packages to use binaries bu
Carlo Segre writes:
>>> An alternative which would remove the inconsistency is to make the
>>> decision that contrib packages will not be built by the officeial
>>> buildd network but have to be built as non-free packages are, on the
>>> unofficial buildd network.
>> If my understanding is current
Heya,
[CC/M-F-T -release@ set, don't see why this needs to be on -devel]
Clint Adams writes:
> I do not really know what you are talking about, but I do not
> want the kids on the playground calling me a coward, so you
> clearly have given me no choice but to accept your offer.
> Unless you want
Luk Claes writes:
> You seem to send the message that you can judge from the sideline how
> things should be run, so I hereby invite you to join the Release Team
> and do a proper job.
>
> If you don't take the challenge I'll interpret that as you being a
> coward who does not deserve to be heard
gregor herrmann writes:
> On Tue, 23 Feb 2010 23:04:22 +, Roger Leigh wrote:
>> 5) buildd has been synched with the buildd code in use on the Debian
>> buildd infrastructure, and is now in use on most, if not all,
>> running buildds. It has undergone extensive changes since the
>>
Stefano Zacchiroli writes:
> On Mon, Feb 15, 2010 at 07:15:52PM +0100, Toni Mueller wrote:
>> On Mon, 08.02.2010 at 20:13:48 +0100, Marc Brockschmidt
>> wrote:
>> > we wish to freeze only after the number of these bugs has dropped below
>> > the mark of 300. As you can see on the usual overview
Heya,
As I'm one of the people who have at some point volunteered to help with
the dev-ref, but mostly failed to actually do work, I guess I could say
a few words, without any pretense of actually knowing better than all
the other people who have already commented...
Lucas Nussbaum writes:
> OK,
Steffen Joeris writes:
> On Wed, 26 Aug 2009 06:51:48 am Marc 'HE' Brockschmidt wrote:
>> Release Goals
>> =
[...]
>> - kFreeBSD:
>> Debian 6.0 Squeeze should be the first Debian release shipping with
>> a non-Linux kernel.
> Out
Sandro Tosi writes:
> On Fri, Jul 17, 2009 at 00:27, Joerg Jaspert wrote:
>> First there wasnt much notice (as people already said), but also second:
>> The thing most important for us DDs, which is for the day-to-day work
>> the upload queue, is pointed elsewhere during that time, to allow you
>>
retitle 456924 O: libgstreamer-perl -- Perl interface to the gstreamer
noowner 456924
thanks
Heya,
In my quest to get rid of tasks I don't have the motivation to actually
work on, I want to give up some of my packages. Basically, there are
three groups: Packages that are just fine and need a main
[This doesn't affect the actual issue, so redirected to just -devel
again]
Neil Williams <[EMAIL PROTECTED]> writes:
> Stefano Avallone <[EMAIL PROTECTED]> wrote:
>> while trying to install kdesvn from experimental, I got the following
>> error:
> Please report a bug against kdesvn - severity impo
Robert Millan <[EMAIL PROTECTED]> writes:
> It seems we relied primarily on the release team, which has betrayed
> the goals of the project,
I do not accept to be called names because I firmly believe that
Debian's goal is to distribute the best possible free software to our
users. All of our wor
Ben Finney <[EMAIL PROTECTED]> writes:
> Have I missed some announcement that DFSG violations don't matter for
> the release of ‘lenny’?
No, because they generally matter.
> I ask because a whole lot of bug reports of DFSG violations have been
> tagged ‘lenny-ignore’ without explanation:
[...]
>
Neil Williams <[EMAIL PROTECTED]> writes:
> I'm assuming there are records of unblocks beyond the mailing list
> archive?
The release team's hint files are available:
http://ftp-master.debian.org/testing/hints/
In this case:
testing/hints/luk:unblock gossip/1:0.31-1
We move hints that were done
"Michael Gilbert" <[EMAIL PROTECTED]> writes:
> I suggest that, by default, the release-critical tracker page list
> only those bugs that do not have a fix uploaded yet (make it optional
> to list all current RC issues).
Try the alternative interface on http://bts.turmzimmer.net, which
provides ev
Aníbal Monsalve Salazar <[EMAIL PROTECTED]> writes:
>>>and one a month old,
>>
>>An upstream contributor promised to fix it and I'm waiting for a patch to
>>test the fix.
> There is a workaround and the RC bug could be downgraded to important.
No. Having a workaround in the bug log is not somethin
Andreas Henriksson <[EMAIL PROTECTED]> writes:
> The previous discussions has lead nowhere. No use in discussing it yet
> again, instead it's time to act!
Put down that crack pipe. Now.
> I offer to fix up all packages to exim4 | mail-transport-agent *and*
> when there is a working default-mta pr
John Goerzen <[EMAIL PROTECTED]> writes:
> Back in the Old Days when I ran an Alpha buildd (years ago), things
> never got automatically marked not-for-us; that happened manually.
> After asking around on IRC a few weeks ago, there is no longer consensus
> that's how it happens now. Does anybody k
Wolf Wiegand <[EMAIL PROTECTED]> writes:
> Marc 'HE' Brockschmidt wrote:
>> For some time now, I have been thinking about the problem of packages
>> which are removed from the archive at some point, without an (enforced)
>> transition to a new package n
Ron Johnson <[EMAIL PROTECTED]> writes:
> On 05/29/08 08:01, Marc 'HE' Brockschmidt wrote:
>> Lucas Nussbaum <[EMAIL PROTECTED]> writes:
>>> I usually run 'apt-show-versions | grep -v uptodate' to find them. The
>>> remaining list is sh
Lucas Nussbaum <[EMAIL PROTECTED]> writes:
> On 29/05/08 at 13:24 +0200, Marc 'HE' Brockschmidt wrote:
>> For some time now, I have been thinking about the problem of packages
>> which are removed from the archive at some point, without an (enforced)
>> trans
Heya,
For some time now, I have been thinking about the problem of packages
which are removed from the archive at some point, without an (enforced)
transition to a new package name. Users of such packages keep them
around, usually never noticing the fact that no security (or other)
support is avai
Goswin von Brederlow <[EMAIL PROTECTED]> writes:
> I would like to suggest a new release goal
The release goal list is frozen. We will only drop goals, not add new
ones.
Marc
--
Fachbegriffe der Informatik - Einfach erklärt
287: Palestinänsertipper
1 Anschlag pro Minute. (Bodo Eggert)
p
"Bernhard R. Link" <[EMAIL PROTECTED]> writes:
> * Steve Langasek <[EMAIL PROTECTED]> [080315 21:12]:
>> $ cat /srv/ftp.debian.org/queue/reject/rhinote_0.7.0-2_i386.reason
>> Rejected: md5sum and/or size mismatch on existing copy of
>> rhinote_0.7.0.orig.tar.gz.
>> Rejected: can not overwrite exi
Mike Bird <[EMAIL PROTECTED]> writes:
> Your English is much better than my German. Nevertheless either your
> English is inadequate for the role you are attempting to fill or else
> you are deliberately trying to provoke an argument.
My english has its flaws, but I'm usually able to follow a
dis
Frans Pop <[EMAIL PROTECTED]> writes:
> Marc 'HE' Brockschmidt wrote:
>> You seem to believe that Frans decides if and when we are going to
>> switch to a dep-based init system.
> That is a completely ridiculous simplification of Mike's mail and also does
&g
[Not CCing -dpkg anymore, not relevant there]
Mike Bird <[EMAIL PROTECTED]> writes:
> Triggers are "needed" - a necessary condition, or at least a highly
> desirable condition - for efficient installation of packages in order
> to avoid unnecessary repetitive global reorderings of the initscript
>
Mike Bird <[EMAIL PROTECTED]> writes:
> Ian hijacked his own program back from the people who had been blocking
> updates for six months - including the triggers enhancement which is
> needed for boot time improvements
dpkg triggers are nice to have, but they are not the reason why we
haven't swi
Riku Voipio <[EMAIL PROTECTED]> writes:
> For the second point, armel must keep up-to-date and must not have
> build failures affecting armel. The current buildds are struggling to
> keep upto date, so 4 new Thecus machines have now been ordered to be set
> up as normal/testing/security buildds and
Michael Casadevall <[EMAIL PROTECTED]> writes:
> What about simply decoupling mips/mipsel's version numbers so an out of
> date package on mips(el) doesn't stall out the rest of the
> testing. Having (somewhat) setup britney/update_out to generate testing
> for m68k, it should just be a matter of
Charles Plessy <[EMAIL PROTECTED]> writes:
> Would it be possible to allow the migration in testing of the package
> that are waiting for being build on mips or mipsel until the buildd
> problem is fixed?
Same answer as a few days ago: No.
Marc
--
Fachbegriffe der Informatik - Einfach erklärt
24
Charles Plessy <[EMAIL PROTECTED]> writes:
> For the moment, the answer is:
>
> As a side effect trying to build ghc6 on MIPS, many (hundreds?) other
> packages are blocked from migrating to testing for more than a month.
Eh, what? You think that mips* is the problem here? What about the
missi
Vincent Danjean <[EMAIL PROTECTED]> writes:
> So, I've two questions:
> - can someone tell me why paje.app has not been tried on mipsel ? What
> should I do ?
Due to kernel problems, the mips* buildds haven't been very reliable in
the past few weeks, creating a lng backlog of packages that
martin f krafft <[EMAIL PROTECTED]> writes:
> also sprach Lars Wirzenius <[EMAIL PROTECTED]> [2008.02.26.1018 +0100]:
>> I don't think a stuff Tux belittles Linux. I don't think a stuffed
>> animal would belittle Debian.
> Fine. I have other arguments: it would make it "yet another FOSS
> project w
"cobaco (aka Bart Cornelis)" <[EMAIL PROTECTED]> writes:
> "As long as there's interest the software will stay alive" is one of the
> main tenets of Free Software. Consequently, IMHO, as long as there's people
> willing to maintain it, it shouldn't be removed regardless of how old it
> is.
GNO
Michael Meskes <[EMAIL PROTECTED]> writes:
> On Mon, Jan 07, 2008 at 03:45:29PM +0100, Cyril Brulebois wrote:
>> On 07/01/2008, Michael Meskes wrote:
>>> Now the question ariss, what went wrong? And also of course could
>>> someone please reschedule this package or do whatever is needed to get
>>>
Luk Claes <[EMAIL PROTECTED]> writes:
> Roger Leigh wrote:
>> Does anyone know where the sources for the current version of
>> wanna-build in use on our buildds may be found?
> The current version is the one of the repository you mentioned. If you
> mean the experimental version, well I suppose tha
Raphael Geissert <[EMAIL PROTECTED]> writes:
> Brendan O'Dea <[EMAIL PROTECTED]>
>perl-base
That's a false positive. Please also take a look at Pre-Depends. Or
simply let off of this effort, the number of false positives is
enormous.
Marc
--
BOFH #343:
The ATM board has run out of 10 pound n
Anthony Towns <[EMAIL PROTECTED]> writes:
> On Sun, Nov 11, 2007 at 07:12:35PM +0100, Marc 'HE' Brockschmidt wrote:
>> I believe it to be one of the more important bits of a standard Unix
>> *desktop* installation - but this just reminds me of the fact that I'm
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Sun, Nov 11, 2007 at 07:12:35PM +0100, Marc 'HE' Brockschmidt wrote:
>> Russ Allbery <[EMAIL PROTECTED]> writes:
>>> Also, do we really need *any* printing system as priority: standard? It's
>>>
Russ Allbery <[EMAIL PROTECTED]> writes:
> Also, do we really need *any* printing system as priority: standard? It's
> not clear to me that printing is still really part of a standard Unix
> installation, even for desktop users (and it definitely isn't for
> servers).
I believe it to be one of th
Lars Wirzenius <[EMAIL PROTECTED]> writes:
> pe, 2007-08-17 kello 10:07 +0200, Romain Francoise kirjoitti:
>> It seems to me that the time spent to generate it on the buildds is
>> probably insignificant compared to the total time needed to build
>> the package... And since generating it can be do
Ron Johnson <[EMAIL PROTECTED]> writes:
> On 08/06/07 07:32, Marc 'HE' Brockschmidt wrote:
> [snip]
>> That will not work. ar(1) is GNU ar on most systems, while dpkg uses
>> ar-as-in-BSD-ar. The diffeences are subtle, but lead to problems in
>> some
"Mathieu Malaterre" <[EMAIL PROTECTED]> writes:
> On 8/6/07, Antti-Juhani Kaijanaho <[EMAIL PROTECTED]> wrote:
>> On Mon, Aug 06, 2007 at 12:34:40PM +0200, Mathieu Malaterre wrote:
>>> I am currently working on integrating debian packaging system in
>>> cpack (part of CMake, see cmake.org). Basic
Oleg Verych <[EMAIL PROTECTED]> writes:
>> Please either address the points raised by the message you're replying
>> to, or don't.
> IMHO that message was a hand waving not deserving reading. Thus i
> dissagre, that i didn't addressed its points in my reply.
If you feel there were no points raised
Gerrit Pape <[EMAIL PROTECTED]> writes:
> Hi, I know that the git-core package doesn't support binNMUs, and AFAIK
> there's no convenient way to change that, as it builds arch: all package
> that depend on the specific arch: any package.
>
> http://bugs.debian.org/423041
>
> Loosening the dependen
Russ Allbery <[EMAIL PROTECTED]> writes:
> Looking at build logs on i386, the common problem for many seems to be
> variations of:
>
> dh_strip
> strip: unable to copy file
> 'debian/libwebauth-perl/usr/lib/perl5/auto/WebAuth/WebAuth.so' reason:
> Permission denied
>
> I can't duplicate this with
Daniel Burrows <[EMAIL PROTECTED]> writes:
> On Sun, Jun 17, 2007 at 01:01:27PM +0200, Vince H&K <[EMAIL PROTECTED]> was
> heard to say:
>> Daniel Burrows wrote:
>>> If I don't hear about any show-stoppers in the next week or so, I'll
>>> upload the new version of aptitude to unstable. Positive
Lucas Nussbaum <[EMAIL PROTECTED]> writes:
> On 13/06/07 at 15:19 +0100, Paul Wise wrote:
>> On 6/13/07, Lucas Nussbaum <[EMAIL PROTECTED]> wrote:
>> >It would be easy to get the list of packages that haven't reached
>> >testing in the n months (and have been in debian for more than n months).
>> S
Lucas Nussbaum <[EMAIL PROTECTED]> writes:
> On 13/06/07 at 11:19 +0200, Andreas Barth wrote:
>> * Lucas Nussbaum ([EMAIL PROTECTED]) [070612 23:17]:
>>> On 12/06/07 at 22:23 +0200, Luk Claes wrote:
unstable is meant for packages that should be in the next stable release,
as such only pa
"Gustavo Franco" <[EMAIL PROTECTED]> writes:
> On 6/12/07, Steve Langasek <[EMAIL PROTECTED]> wrote:
>> On Tue, Jun 12, 2007 at 04:40:54PM -0300, Gustavo Franco wrote:
* What do you mean by "switch unstable automatic nature to not
automatic"
>>> In a few words, move the 'NotAutomatic: yes
Pierre Habouzit <[EMAIL PROTECTED]> writes:
> On Tue, Jun 12, 2007 at 10:57:17PM +0900, Charles Plessy wrote:
>>> There's also the fact that if you remove experimental it's easy enough
>>> for people to set up their apt repositories somewhere if they want to
>>> provide packages outside of unstable
Loïc Minier <[EMAIL PROTECTED]> writes:
> On Mon, Jun 04, 2007, Raphael Hertzog wrote:
>> Library maintainers are supposed to maintain the *.symbols file. For
>> this, they have to create files "debian/.symbols."
>> (dpkg-gensymbols will try too fallback to "debian/symbols.",
>> "debian/.symbols"
"Miriam Ruiz" <[EMAIL PROTECTED]> writes:
>> Apart from that gothic fonts were forbidden by law in 1941 and replaced by
>> latin type of lettering. So the feeling is really nothing more than a
>> feeling in this case.
> I can't believe that... gothic fonts are forbidden in Germany by law!!!???
No.
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> On Wed, 30 May 2007 18:28:43 +0200, Raphael Hertzog <[EMAIL PROTECTED]> said:
>> What Guillem said is that checklib also indicated binaries which are
>> linked against a library without using any of its symbols. Thus the
>> binary shouldn't have been
Andreas Tille <[EMAIL PROTECTED]> writes:
> On Mon, 14 May 2007, Francois-Denis Gonthier wrote:
>>> Beware that in (at least fr_FR) french, "gastro" is also a shortcut
>>> for "gastroenteritis" and is strongly associated with its symptoms!
>>> It may really hamper your success in french-speaking co
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Thu, 10 May 2007, Marc 'HE' Brockschmidt wrote:
>> Raphael Hertzog <[EMAIL PROTECTED]> writes:
>>> On Wed, 09 May 2007, Gustavo Franco wrote:
>>>> I don't think that it will be accepeted as
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Wed, 09 May 2007, Gustavo Franco wrote:
>> I don't think that it will be accepeted as art.debian.org though, not
>> ugly enough yet.
> What does that mean ?
Usually the web services on debian.org hosts provide access to quite
ugly pages. See -www fo
Junichi Uekawa <[EMAIL PROTECTED]> writes:
> (B) A unique IP represents a single system (Even though DHCP may
> change IP address over a month's period, NAT may share IP addresses).
That does look wrong. At least here in Germany, most broadband users get
a new IP every 24 hours, so a single user c
Holger Levsen <[EMAIL PROTECTED]> writes:
> On Friday 16 March 2007 00:49, Steve Langasek wrote:
>> A large fraction of bug reports are bad or incomplete, so you need to
>> ensure that you can contact bug submitters for more information.
>>
>> HTTP doesn't give you a callback mechanism, so you need
Heya,
I certainly agree with some of things you said, as I also believe that
Debian could profit from better management and/or planning in some
areas, I don't think this would have made the timely release of etch
possible.
Josselin Mouette <[EMAIL PROTECTED]> writes:
> Back in September, it seeme
Charles Plessy <[EMAIL PROTECTED]> writes:
> Le Fri, Feb 23, 2007 at 08:36:26AM -0500, Matthias Julius a écrit :
>> John Goerzen <[EMAIL PROTECTED]> writes:
>>> Would it be possible to record the name of the human that marked the
>>> package in debian/changelog? That would be a big help, I think (
Greg Folkert <[EMAIL PROTECTED]> writes:
> Seems I am not the only one that believes GNOME is limiting.
>
> Linus Torvalds has submitted patches. I am betting they get ignored or
> rejected with "to complex for our idiot users".
>
> Yes, Joss could you please explain this away for me?
Errrm, I kno
Greg Folkert <[EMAIL PROTECTED]> writes:
[...]
> I am sure yoush hasn't done a thing with it, as Experimental packages
> don't need to be maintained, period.
Bullshit. Experimental is a playground, not a graveyard for development
releases. It's supposed to be used as a testing ground for unstable,
Jari Aalto <[EMAIL PROTECTED]> writes:
[wether to use $() or ``]
> Le't call this "wishlist" if we need to be pedantic. I would still
> call this a bug from a QA perspective. Quality is more than "valid
> syntax".
This is not a bug. Not even wishlist. Even discussing this issue is a
senseless wast
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Sun, 28 Jan 2007, Florian Weimer wrote:
>> Is their a developer-accessible mirror (on a non-restricted host) of
>> the archive maintenance which are in production, including (most of)
>> the configuration?
> dak is managed in a bzr repository:
> http
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 o
Luca Capello <[EMAIL PROTECTED]> writes:
> 2) the Debian menu requires xpm icons [2] and in fact only 4 packages
>have icons in the png format (ekiga, evince, gimp, gnomemeeting),
To be fair, the .png icon referenced by the evince menu file doesn't
exist...
> 4) evince doesn't appear by defau
Mike Hommey <[EMAIL PROTECTED]> writes:
> As a lot of gnome 2.16 currently in experimental has been uploaded for
> amd64, there's a lot of it not built for x86 yet.
>
> I heard several times people claim experimental was autobuilt, but are
> there any x86 autobuilder set up for experimental ?
Ther
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Mon, Dec 04, 2006 at 02:45:26AM +, Stephen Gran wrote:
>> You need Pre-Depends only when a package must be configured before your
>> postinst is run. In the case of a perl module, I would think it only
>> needs to be unpacked.
> No, you need a Pr
Gunnar Wolf <[EMAIL PROTECTED]> writes:
> Marc 'HE' Brockschmidt dijo [Sun, Dec 03, 2006 at 11:47:45AM +0100]:
>>>> use File::Find;
>>> Provided by perl-modules, which is build-essential. However, this
>>> module is used at installation time (in
Mike Hommey <[EMAIL PROTECTED]> writes:
> Considering that the maintainer scripts have not been inherited from
> mozilla, and that the mozilla engine is pretty different, may I just
> close all the bugs assigned to old mozilla packages, requesting a
> reopen if the bug still exists in iceape ?
I b
Gunnar Wolf <[EMAIL PROTECTED]> writes:
>> use File::Find;
> Provided by perl-modules, which is build-essential. However, this
> module is used at installation time (in postinst), so yes, this should
> be listed as a pre-depends (as it's not a required/essential package)
Why exactly do you need a
close 369605
thanks
"Francisco Moya" <[EMAIL PROTECTED]> writes:
> Package zeroc-icee-translators lists an outstanding bug #369605 filed
> 63 days ago. I don't know how to properly handle this situation
> since:
> - It was actually a bug report against package zeroc-ice.
No, it wasn't. it was
Tyler MacDonald <[EMAIL PROTECTED]> writes:
[...]
> 1. If you #include a header directly, you have to depend on that
> package.
[...]
> 4. If you #include a header that doesn't belong to *any* package
> (including the source package you're currently building), that's just
> outright evi
retitle 360583 O: blam -- an RSS aggregator for GNOME
Johan Svedberg <[EMAIL PROTECTED]> wrote:
> I'm no longer maintaining blam. I've sent out a RFA[1] but it doesn't
> seem like anyone has picked it up.
If you are not intending to maintain the package, you should orphan it,
not ask for an adopte
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
"curt manucredo (hansycm)" <[EMAIL PROTECTED]> writes:
> II.B. on the upload and storage side
>
>
> the upload process may need some more changes though (e.g.: for
> automation). if this ever comes true, there will have to be a period of
> time where both, the
Heya,
Michael Meskes <[EMAIL PROTECTED]> writes:
[Java flamewar]
> DPL, I wonder Why the Sun-Java package is not handled the same as any
> other package. What makes it so special that it deserves special
> treatment?
>
> Isn't this a discrimination against all other packages? :-)
ACK. This is the
Hi *DPL*,
Anthony Towns writes:
> On Wed, May 17, 2006 at 11:09:30PM -0700, Don Armstrong wrote:
>> First off, I'm going to completely ignore the FAQ as the FAQ and the
>> license both specifies that the FAQ does not have any legal validity.
> Repeating frequently asked questions that have alread
Roberto Lumbreras <[EMAIL PROTECTED]> writes:
[...]
> Ok, the maintainer has not fixed the bugs, has not packaged the last
> version of it in time, etc, but he has done a great job anyway, and I
> still don't see the point of hijacking the package.
So he has done not one of the things expected of
Sven Luther <[EMAIL PROTECTED]> writes:
> On Thu, May 11, 2006 at 01:10:16AM +0100, Steve McIntyre wrote:
>> Unfortunately, other mailing list discussions have been less
>> happy. A somewhat acrimonious argument between Sven Luther and members
>> of the d-i team spread out across various lists, sta
Pjotr Kourzanov <[EMAIL PROTECTED]> writes:
> I am adding some additional archs to my local installation like i386-uclibc,
> which makes hurd-i386 an exception to the rule of having the CPU arch first
> and the OS name the next.
There's also kfreebsd-{i386,amd64}, so why don't you use uclibc-i386?
"Krzysztof Krzyzaniak (eloy)" <[EMAIL PROTECTED]> writes:
> * Package name: libtest-use-ok-perl
[...]
> Description : Alternative to Test::More::use_ok
>
> According to the Test::More documentation, it is recommended to run use_ok()
> inside a BEGIN block, so functions are exported at c
"Joseph Smidt" <[EMAIL PROTECTED]> writes:
> Once every three months the new "Pre-Stable" distro will upload only
> those packages from testing that have had 0 RC bugs for at least month
> and have been flagged by their maintainers as a good version to entet
> stable.
This would mean, with a year
Miles Bader <[EMAIL PROTECTED]> writes:
> Jari Aalto <[EMAIL PROTECTED]> writes:
>> The Perl syntax is elegant, efficient and Python's regexp handling is
>> nowhere as intuitive as needed for day-to-day tasks where the poer is
>> needed.
> Efficient, perhaps, but _elegant_?!? HAhahahahah1hahah3$I1
1 - 100 of 155 matches
Mail list logo
