; this DEP otherwise they would have to patch lintian to support the
> differing field and it seems counter-productive.
That sounds like a pretty bad way to force them to make changes to an
existing policy.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
|
On 19/06/09 at 11:14 +0200, Josselin Mouette wrote:
> Le vendredi 19 juin 2009 à 11:03 +0200, Lucas Nussbaum a écrit :
> > > I did not contact them yet. I expect that they will follow the outcome of
> > > this DEP otherwise they would have to patch lintian to support the
>
ian yet , and I'll be looking for
a sponsor shortly. If somebody is interested, drop me a note ;)
[0] https://wiki.ubuntu.com/MultiDistroTools
[1] http://tiber.tauware.de/~lucas/versions/unstable-experimental.html
[2] http://tiber.tauware.de/~lucas/versions/
--
| Lucas Nussbaum
| [EMAIL PRO
en by the Debian/Ruby Extras team.
--
| Lucas Nussbaum
| [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 29/02/12 at 17:19 +0100, Sylvestre Ledru wrote:
> To answer to a question that I received in private, I updated Lucas
> Nussbaum's scripts [1] to manage clang outputs. I will merge that in the
> svn once I will be sure I won't mess up between gcc & clang outputs.
> The list on clang.d.n are gene
Hi,
On 22/06/12 at 09:37 +0200, Stefano Zacchiroli wrote:
> On Fri, Jun 22, 2012 at 12:29:48AM -0400, Yaroslav Halchenko wrote:
> > I was thinking about a bit more automated way... ideally (in the long
> > run) even that FTBFS (e.g. due to failed tests or some other arch
> > specific quirks) would
On 22/06/12 at 10:56 +0200, Goswin von Brederlow wrote:
> Are archive wide rebuilds done on anythiong but i386/amd64?
A long time ago, I played with archive rebuilds inside qemu for mips or
mipsel. It is probably doable, but needs someone to do the work.
Lucas
--
To UNSUBSCRIBE, email to debia
ntial, it is a
> bug to explicitly depend on bash, and after the change it will be a
> bug to not depend on bash.
It won't: bash stays the default shell for interactive use, so it stays
essential as well.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/
> > * and performing another archive-wide checkbashisms check on binary
>
> Checkbashisms is a lintian check, right?
No, it's in devscripts.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F
On 29/06/09 at 22:53 +0200, Raphael Hertzog wrote:
> Lucas Nussbaum suggested to replace "Bug-" with "" while
> Sean Finney suggested that the latter could be an alias for the former. I
> explained that I initially selected "Bug-" because it enables simp
be it would help to use RT to track questions to da-mana...@d.o
instead of pure email?
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.or
stion. What do other people think of it?
I think that this information should be stored outside of the patch (in
the history of a VCS, for example).
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
e integrated when generating
new.html. I could also mention it if last_modified >> arrival, which
indicates that the bug was modified (possibly by additional comments).
[1] http://udd.debian.org/
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu..
e nice, yes. Choose them wisely, as many people will
probably just copy/paste from them. :-)
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian
ses it on the libraries side.
(see the recent thread on debian-ruby@ for the details)
Of course, you are welcomed to help instead of just bitching.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B
and bootstraps Mercury from
> the source distribution. It requires gcc-3.4 as a build-depend and is
> able to bootstrap itself so that the resulting binaries are optimal on
> 32bit and 64bit machines (the explanation involves a discussion of
> tagged pointers).
Hi,
gcc-3.4 is about t
Package: wnpp
Severity: wishlist
Owner: Lucas Nussbaum
* Package name: ubuntu-dev-tools
Version : 0.75
Upstream Author : Ubuntu developers
* License : Mix. GPLv{2,3} (or later)?
Programming Lang: mostly python, some shell
Description : useful tools for Ubuntu
eems to
> be inactive.
Also, if you run into suspicious packages, that might be candidate for
orphaning and removal, and don't have time to investigate them yourself,
please make a list and send it to debian...@lists.debian.org.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://
corresponding dev-ref
section. (That applies to the i18n chapter of dev-ref, which is
apparently badly outdated).
- Contributing to dev-ref could become a part of the NM process. We
already have a "fix two RC bugs" question. We could have a "fix two
dev-ref bugs&q
.
For (A) and (B), once a proposal has been made, has been seconded by at
least one DD, and some time (e.g one week) has passed to give others the
chance to voice their concerns, the change can be made.
For (C), non-editorial changes should be discussed more widely (on
-devel@ or -project@), and co
knowing better than all
> the other people who have already commented...
>
> Lucas Nussbaum writes:
> > OK, let's try to change the way it is maintained by moving to something
> > similar to policy. Several questions need to be addressed.
> >
> > - Where should
CILL license has such a clause (see 5.3.4 in
http://www.cecill.info/licences/Licence_CeCILL_V2-en.txt).
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debian-devel-requ..
On 09/09/09 at 16:18 +0200, Stefano Zacchiroli wrote:
> On Wed, Sep 09, 2009 at 04:04:16PM +0200, Lucas Nussbaum wrote:
> > Choosing CC BY-SA would nicely conflict with our existing documentation,
> > like the Debian new maintainer guide (GPL2+) or developers-reference
> > (G
ing else, RC bugs should be used
instead.
Also, lots of packages currently in our archive already have those
errors. What do you plan to do with those? If you auto-reject packages
that introduce those errors, it would be logical to file RC bugs and/or
remove them from the archive.
--
| Lucas N
-f "$@", so I
don't see why calling, for example, "debian/rules -d clean" would not
work as expected.
It sounds like several people in this discussion are shooting at an easy
target without looking at the specific details.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum
rmine who
is empowered to take those decisions.
I'm fine with letting ftpmasters take that decision. However, they
should consult the project before adding new tags (mail to -devel: "We
are thinking of adding those new tags to our list, comments?" instead of
a mail to -devel s
bles.
Since this obviously breaks lots of packages, what about changing the
default in binutils-gold instead?
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debia
On 02/11/09 at 12:12 +, Sune Vuorela wrote:
> On 2009-11-02, Lucas Nussbaum wrote:
> >
> >> Tried to build your package and it fails to build with GNU binutils-gold.
> >> The
> >> important difference is that --no-add-needed is the default behavior of of
On 02/11/09 at 13:50 +0100, Peter Fritzsche wrote:
> Lucas Nussbaum wrote:
> > I thought people were supposed to discuss it on -devel@ before starting
> > a MBF?
> What is a MBF?
mass bug filing.
> > Anyway, ways you could have made it better:
> > - provide a step
hat I shouldn't be allowed to edit it.
You probably just need a wiki account.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.o
On 02/11/09 at 12:10 +0200, Faidon Liambotis wrote:
> Lucas Nussbaum wrote:
> > I'm fine with letting ftpmasters take that decision. However, they
> > should consult the project before adding new tags (mail to -devel: "We
> > are thinking of adding those new tags to
I've never seen any aggressiveness towards you or
Josselin, or at least not at all comparable to the shit you give him.
It's a bit too easy to behave like an ass and insult him, and then
complain that he is not talking to you or willing to work with you.
--
| Lucas Nussbaum
| lu...@lucas-n
old that Matthias is currently unable to read/answer
email. So don't put too much hope in a statement from him in the next
hours.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE,
again that people ask that all discussions are public.
We really need to trust Piotr (and others) to do the right thing here.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
Ftpmasters have done a change that possibly has very large side effects.
>From d-d-a:
> Tracking arch all packages
> --
> #246992 asked us to not delete arch all packages before the
> corresponding (if any) arch any packages are available for all
> architectures. Examp
are free to modify it manually during the build.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe&qu
On 05/01/10 at 21:39 +0100, Joerg Jaspert wrote:
>
> > That's only true with the v3 format. If you stick with v1, you can
> > patch debian/control at unpack time.
>
> > And in both cases, you are free to modify it manually during the build.
>
> Err, what? debian/control modified during build? Su
On 05/01/10 at 16:31 -0800, Steve Langasek wrote:
> On Tue, Jan 05, 2010 at 03:52:46PM -0800, Don Armstrong wrote:
> > On Tue, 05 Jan 2010, Lucas Nussbaum wrote:
> > > On 05/01/10 at 21:39 +0100, Joerg Jaspert wrote:
> > > >
> > > > > That's only
On 07/01/10 at 03:08 +0100, Frans Pop wrote:
> Lucas Nussbaum wrote:
> > Anyway, to avoid modifying debian/control directly, it's easy to add an
> > additional substvar (ubuntu:Browser?):
> > debian/control:
> > Depends: [...], iceweasel | ${ubuntu:Browser}
&g
oint of enforcing that when we have
the technology (pbuilder, sbuild + lvm snapshots) there to ignore that
problem.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--
To UNSUBSCRIBE, email to deb
specially now that we have the technical means to solve that issue).
It means that some packages in the archive are silently being built with
additional deps, without any coordinated effort to track them down.
Of course, I'm in favor of doing (2) and building in clean envs on our
own buil
On 20/01/10 at 01:49 +0100, Holger Levsen wrote:
> On Mittwoch, 20. Januar 2010, Lucas Nussbaum wrote:
> > There are two ways to attack that problem:
>
> how about the compromise and doing both, except that for (1) we file the bugs
> with severity important?
There are a lot
On 20/01/10 at 00:48 -0800, Steve Langasek wrote:
> On Wed, Jan 20, 2010 at 02:22:33PM +1300, Lucas Nussbaum wrote:
>
> > Why spend a lot of time on tasks that provide little benefit, and also
> > some disadvantages (in some cases, the fixes might be non-obvious, and
> >
ges[1] from 2008 that probably have a missing build-conflict, since
they produced different binary packages (according to debdiff) in an
unclean chroot. (that list contains some false positives)
[1] http://people.debian.org/~lucas/logs/2008/01/22/bdfh/debdiffs/
--
| Lucas Nussbaum
| lu...@lucas-nus
Hi,
On 14/07/14 at 16:46 +0100, Dominic Hargreaves wrote:
> Hello,
>
> I've agreed to give a one day Debian packaging workshop at $dayjob aimed at
> sysadmins and developers, and I'd be interested in hearing from those who
> have already run similar sessions to get advice/tips for how to approach
Package: wnpp
Severity: wishlist
Owner: Lucas Nussbaum
* Package name: kadeploy
Version : 3.3
Upstream Author : Kadeploy developers
* URL : http://kadeploy3.gforge.inria.fr/
* License : CeCILL version 2.0
Programming Lang: Ruby
Description : Scalable
Hi Marc,
On 31/07/14 at 08:17 +0200, Marc Haber wrote:
> On Wed, 30 Jul 2014 18:02:40 +0200, Lucas Nussbaum
> wrote:
> > Kadeploy is a scalable, efficient and reliable deployment system (cluster
> > provisioning solution) for cluster and grid computing. It provides a set of
>
On 01/08/14 at 13:55 +0200, Marc Haber wrote:
> On Fri, 1 Aug 2014 11:37:28 +0200, Lucas Nussbaum
> wrote:
> >On 31/07/14 at 08:17 +0200, Marc Haber wrote:
> >> On Wed, 30 Jul 2014 18:02:40 +0200, Lucas Nussbaum
> >> wrote:
> >> > Kadeploy is a scalable
On 02/08/14 at 09:51 +0800, Paul Wise wrote:
> On Fri, Aug 1, 2014 at 10:31 PM, Lucas Nussbaum wrote:
>
> > FAI and Kickstart rely on an installation process (even if not
> > debian-installer's): packages are extracted, installed and configured.
> > Kadeploy and Cl
On 25/08/14 at 14:13 -0700, Steve Langasek wrote:
> On Sun, Aug 24, 2014 at 09:28:11AM -0700, Lucas Nussbaum wrote:
> > Debian logo now registered as a trademark
> > =
>
> > Thanks to the work of the Debian trademark team and the
Hi,
On 25/08/14 at 14:46 -0700, Paul Wise wrote:
> On Mon, Aug 25, 2014 at 2:13 PM, Steve Langasek wrote:
>
> > Does this list of expenses mean that you now have a good overview of
> > Debian's cash flow? In April, I understood that this was a major
> > outstanding problem. I'm happy to see tha
Package: wnpp
Severity: normal
Hi,
Following a previous discussion on state of developers-reference[1], I:
- switched the package to git, and moved it to collab-maint;
- went through all bugs with patches;
- fixed a few other bugs;
- reviewed other bugs, fixed some of them, and closed those that
On 17/11/14 at 11:15 -0800, Don Armstrong wrote:
> §6.3.6 does not prevent the CTTE from being presented an issue early. It
> stops the CTTE from deciding an issue before a consensus approach has
> been attempted. In this particular case, I felt that a consensus
> approach had been attempted when t
Hi,
I'm unlikely to be able to do much archive rebuild work in the coming year, so
I would welcome help on that front.
Here is the "job" description:
- maintain scripts to organize archive rebuilds, parse logs and file bugs
Required skills: basic Ruby knowledge (or willingness to learn)
scri
On 09/05/13 at 08:32 +0200, Niels Thykier wrote:
> The execution of the time-based freeze might have failed. Also,
> "testing" did not serving its purpose of "always being in (a
> near-)releasable state"[2] with its 500+ RC bugs at the start of the
> freeze was not ideal (either?).
I think that
On 09/05/13 at 13:20 +0200, Julien Cristau wrote:
> On Thu, May 9, 2013 at 12:55:03 +0200, Lucas Nussbaum wrote:
>
> > Also, we should be more agressive at getting down the number of RC bugs
> > by automatically removing RC-buggy not-so-important packages. For
> > example
On 11/05/13 at 11:37 +0200, Johannes Schauer wrote:
> Hi,
>
> Quoting Paul Wise (2013-05-11 10:40:18)
> > Lucas created a script that displays a list of "important" packages, puppet
> > isn't on that either:
> >
> > http://udd.debian.org/cgi-bin/important_packages.cgi
>
> Not surprising as the a
Hi,
On 20/05/13 at 18:19 +0200, Michael Stapelberg wrote:
> Hello,
>
> In the past, we have had multiple heated discussions involving
> systemd. We (the pkg-systemd-maintainers team) would like to better
> understand why some people dislike systemd.
>
> Therefore, we have created a survey, which
On 22/05/13 at 05:50 +0300, Uoti Urpala wrote:
> Lucas Nussbaum wrote:
> > I went through the various init systems threads again during the last
> > few days. My understanding of the consensus so far is the following:
> >
> > - Both systemd and upstart bring many
On 22/05/13 at 08:22 +, Thorsten Glaser wrote:
> >> As Debian, we have two different problems:
> >> 1. We need to decide which init systems we want to support, and how.
> >> 2. We need to decide which init system should be the default.
>
> We will have a GR about that.
(I assume that by "abou
On 22/05/13 at 14:45 +0200, Josselin Mouette wrote:
> Le mercredi 22 mai 2013 à 08:16 +0200, Lucas Nussbaum a écrit :
> > - there are 300+ upstart job files ready to be imported from Ubuntu
>
> When you compare the time it takes to write an upstart job file or a
> systemd unit
Hi,
On 22/05/13 at 15:11 +0200, Marco d'Itri wrote:
> On May 21, Lucas Nussbaum wrote:
>
> > We don't need to select a single init system at this point, and it would
> As the maintainer of a package which is strongly tied to the init
> system, I disagree.
>
On 23/05/13 at 12:28 +0800, Thomas Goirand wrote:
> On 05/22/2013 04:53 AM, Lucas Nussbaum wrote:
> > - Neither systemd nor upstart are likely to be ported to kfreebsd soon,
> > as they both rely on many Linux-specific features and interfaces.
>
> Though it should be easy
Hi,
On 27/05/13 at 09:13 +0200, Ondřej Surý wrote:
> On Sun, May 26, 2013 at 10:29 PM, Helmut Grohne wrote:
>
> > I find it depressing to see four init/rc systems, of which three are
> > mutually incompatible in every single possible aspect.
> >
>
> Just my two cents.
>
> I would be quite hap
On 02/06/13 at 16:18 +0200, Didier 'OdyX' Raboud wrote:
> Le dimanche, 2 juin 2013 15.54:31, Cyril Brulebois a écrit :
> > Marcin Kulisz (02/06/2013):
> > > Why not to use http://http.debian.net/ ?
> >
> > Surely the .net part of it?
>
> If that's the reason, why do we have cdn.debian.net in the
Hi,
On 27/06/13 at 12:34 +0200, Wouter Verhelst wrote:
> On 25-06-13 07:28, Alexandre Rebert wrote:
> > Hi,
> >
> > I am a security researcher at Carnegie Mellon University, and my team
> > has found thousands of crashes in binaries downloaded from debian
> > wheeze packages.
>
> Out of interest
Hi,
Thanks a lot for this work.
On 30/06/13 at 23:32 +0200, Niels Thykier wrote:
> We are considering removing the following packages from testing as
> they have unfixed RC bugs filed against them. The packages can be
> found in the attached dd-list.
>
> The packages have been selected based on
On 01/07/13 at 15:00 +0200, Johannes Schauer wrote:
> Hi,
>
> Quoting Lucas Nussbaum (2013-07-01 08:21:30)
> > Currently, the following criterias are used:
> > | Key packages are:
> > | - packages whose popcon is higher than 5% of the max popcon (that's
> &g
Hi,
On 15/07/13 at 21:39 +0200, Michael Stapelberg wrote:
> Hi,
>
> I am sorry for starting yet another thread on systemd, but we feel this
> particular post is important and should spread as widely as possible
> (i.e. beyond just readers of planet debian):
>
> http://people.debian.org/~stapelbe
On 16/07/13 at 15:33 +0200, Michael Biebl wrote:
> Hi Lucas,
>
> thanks for your input!
>
> Am 16.07.2013 14:50, schrieb Lucas Nussbaum:
> > Hi,
> >
> > On 15/07/13 at 21:39 +0200, Michael Stapelberg wrote:
> >> Hi,
> >>
> >> I am s
On 30/07/13 at 12:00 -0400, Asheesh Laroia wrote:
> Hi all Debianites,
>
> I've been inspired by the "Developer Advisory Team" in another
> project [1], and so I want to create a similar team within Debian.
> In this email, first I'll summarize what the concept of Developer
> Advisory Team is, and
On 26/08/13 at 10:00 -0300, gustavo panizzo wrote:
> On 08/26/2013 07:33 AM, Neil McGovern wrote:
> > I'm hoping that these raising of hands are also offers to help do the
> > work to make it happen.
> i offer help, we are interested on longer maintenance for some packages.
> i think we should sta
On 28/08/13 at 22:58 +0200, Joerg Jaspert wrote:
> Hello Debian world,
>
> there is currently a discussion within the FTP Team and we appear to
> have two opinions on it. As we are open on the outcome and it basically
> affects the whole project, we came up with the following summary to
> solicit
On 04/09/13 at 12:13 +0900, Norbert Preining wrote:
> On Mi, 04 Sep 2013, Ben Hutchings wrote:
> > How much do those packages weigh, Norbert? Are TeX transitional
> > packages particularly heavy?
>
> In kg? In bit? In work time?
>
> > I really don't know why you think TeX is exempt from the usua
On 04/09/13 at 20:52 +0900, Norbert Preining wrote:
> On Mi, 04 Sep 2013, Holger Levsen wrote:
> > which other binary packages build by texlive-lang do you consider
> > "pathological to use"?
>
> I considered the installation of one -lang package by itself without
> actual latex package pathologi
On 11/09/13 at 22:09 +0200, Lucas Nussbaum wrote:
> Participation in OpenZFS initiative
> ===
> Debian was invited to participate in the OpenZFS community[1].
> Interestingly, Debian supports ZFS on Debian GNU/kFreeBSD, and on Debian
> GNU/Linu
On 08/10/13 at 19:36 +, Bill Allombert wrote:
> On Tue, Oct 08, 2013 at 07:58:03AM +0100, Neil Williams wrote:
> > rc-alert has existed for quite some time and it gets the alert in
> > *ahead* of package removal. It alerts users to the real problem - the
> > RC BUG!
>
> Did you try to run rc-a
On 24/10/13 at 15:18 +0200, Gabriel de Perthuis wrote:
> Hello,
> I've written a tool to import Debian packages into Git:
>
> git clone deb::mypackage
>
> It does a faithful import of the package history from
> snapshot.debian.org. There is some agressive caching built-in, and a
> bit of log
Hi,
On 24/10/13 at 16:40 +0100, Steve McIntyre wrote:
> Hi folks,
>
> This goes back to during the wheezy release cycle. There was a little
> discussion around a change in tasksel [1], but rather too late in the
> day for the change to make sense. Now we have rather more time, I
> feel. Let's cha
On 24/10/13 at 17:40 +0100, Dmitrijs Ledkovs wrote:
> On 24 October 2013 17:38, Svante Signell wrote:
> > On Thu, 2013-10-24 at 18:31 +0200, Lucas Nussbaum wrote:
> >
> >> What's the the status of XFCE regarding accessibility?
> >>
> >> That was a bi
On 25/10/13 at 12:33 +0200, Josselin Mouette wrote:
> Le jeudi 24 octobre 2013 à 18:50 +0200, Lucas Nussbaum a écrit :
> > > > An even stronger reason to move away from Gnome if the classic mode
> > > > disappears.
I just wanted to point out that this quote is no
On 25/10/13 at 12:16 -0400, Paul Tagliamonte wrote:
> In response to the recent threads, I'd like to ask the tech-ctte to
> please vote on and decide on the default init system for Debian.
I agree. I don't think that many substantial new arguments are going to
be brought by waiting more on this to
On 28/10/13 at 18:21 -0700, Russ Allbery wrote:
> Wouter Verhelst writes:
>
> > Also, since all alternative init implementations under consideration do
> > support sysv-style init scripts, I think that whatever init system we
> > (well, you, the TC) end up choosing, the requirement in policy shou
On 29/10/13 at 22:42 +0100, Emilio Pozuelo Monfort wrote:
> On 24/10/13 18:31, Lucas Nussbaum wrote:
> > What's the the status of XFCE regarding accessibility?
> >
> > That was a big strengh of GNOME for a long time, though I've heard
> > rumors (sorry not
On 28/09/12 at 18:48 +0200, Arno Töll wrote:
> Hello,
>
> we may all agree that the maintenance of some (many?) packages in Debian
> is in a unclear situation. There is a transient state, where people are
> interested to bring a package in shape but the strong role of a package
> maintainer in Deb
On 11/10/12 at 05:50 +, Bart Martens wrote:
> | Anyone can mark a package as orphaned after the following steps have been
> | completed : Someone submits an "intent to orphan" (ITO) in the bts with
> an
> | explanation of why he/she thinks that the package needs a new
> maintainer.
On 11/10/12 at 18:44 +0900, Charles Plessy wrote:
> Le Thu, Oct 11, 2012 at 05:50:51AM +, Bart Martens a écrit :
> >
> > | Anyone can mark a package as orphaned after the following steps have
> > been
> > | completed : Someone submits an "intent to orphan" (ITO) in the bts
> > with an
On 11/10/12 at 10:21 +0200, Gergely Nagy wrote:
> Lucas Nussbaum writes:
>
> > On 11/10/12 at 05:50 +, Bart Martens wrote:
> >> | Anyone can mark a package as orphaned after the following steps have
> >> been
> >> | completed : Someone submits
On 11/10/12 at 11:27 +0200, Arno Töll wrote:
> Hi,
>
> On 11.10.2012 07:50, Bart Martens wrote:
> >> - the submitter of the "intent to orphan" bug must Cc
> >> debian...@lists.debian.org, and file the bug with severity:serious (this
> >> was part of the "criterias" proposal).
> > | Anyone
On 11/10/12 at 22:18 +, Sam Hartman wrote:
>
> For myself, I'd feel a lot more comfortable with DDs seconding than DMs
> seconding.
>
> In my mind, when you sign up to be a DM, you're signing up to do a good
> job of maintaining one or more packages.
>
> In my mind a part of the additional c
Hi,
Here is an attempt at summarizing & building a proposal out of the
"Hijacking^W^W^W^W^W^WSalvaging packages for fun and profit: A proposal"
thread that was started at [1].
The following aims at being written in a form suitable for inclusion in
developers-reference.
-
On 24/10/12 at 08:17 -0400, Scott Kitterman wrote:
> That could work either way. If you're in such a rush to build consensus you
> could change 3/1 ACK/NACK ratio to without objection (objections result in
> disputes resolved by the tech ctte) and have a +1 from me.
>
> The problem is that onc
On 23/10/12 at 17:19 +, Sune Vuorela wrote:
> On 2012-10-23, Lucas Nussbaum wrote:
> > Hi,
> >
> > Here is an attempt at summarizing & building a proposal out of the
> > "Hijacking^W^W^W^W^W^WSalvaging packages for fun and profit: A proposal"
>
Hi,
According to the huge thread starting at
https://lists.debian.org/debian-devel/2012/10/msg00469.html, it seems that:
- there's consensus that a lightweight process for orphaning unmaintained
packages is a good idea (if you are not convinced yet, I urge you to read
Russ' post at https://lis
On 05/03/13 at 16:40 +0100, Enrico Tassi wrote:
> I'm new to the art of packaging with git, and I found a little issue
> I'm unable to solve nicely.
>
> I'm in the usual situation, the package and the upstrem are under git.
> Thus I have two remotes in my original repository:
>
> origin ss
Hi,
On 14/04/13 at 00:00 +, devo...@vote.debian.org wrote:
> The winners are:
>Option 3 "Lucas Nussbaum"
I feel of mix of happiness (being very honored of being elected) and of
fear (being a bit scared of the importance of the task)!
I would like to thank:
- Gerge
Hi,
On 04/05/13 at 10:10 +0100, Wookey wrote:
> +++ brian m. carlson [2013-05-03 21:39 +]:
> > On Sat, May 04, 2013 at 12:10:25AM +0300, Timo Juhani Lindfors wrote:
> > > "Bernhard R. Link" writes:
> > > > Once we drop that and only give people the right to modify the
> > > > software we dist
On 04/05/13 at 12:27 -0400, Michael Gilbert wrote:
> On Sat, May 4, 2013 at 12:14 PM, Andrey Rahmatullin wrote:
> > On Sat, May 04, 2013 at 12:05:06PM -0400, Michael Gilbert wrote:
> >> Again, as Thijs argued somewhat eloquently already earlier in this
> >> thread, computational time is not the sca
On 05/05/13 at 03:06 +0200, Adam Borowski wrote:
> On Sun, May 05, 2013 at 10:00:07AM +0900, Charles Plessy wrote:
> > Anyway, given that our infrastructure builds binary packages from a fresh
> > unpacked source package, I would prefer if we keep the compromise that
> > imperfect "clean" targets a
On 27/09/10 at 10:14 +0200, Stefano Zacchiroli wrote:
> On Wed, Sep 22, 2010 at 01:19:20PM -0700, Don Armstrong wrote:
> > On Wed, 22 Sep 2010, Stefano Zacchiroli wrote:
> > > From what concerns the BTS, Don's proposal in [2] (the main one, not
> > > the alternative solution) seems reasonable to me
201 - 300 of 581 matches
Mail list logo
