On Wed, 2020-12-09 at 19:31 +0100, Mattia Rizzolo wrote:
>
> Even then, the message says that "cluster3 has no binaries on any
> arch"
> - from there why can't one try to figure why there are no binaries?
> I'm
> positive that dumping the tracker link and that message in
> debian-mentors@ would y
On Wed, Dec 09, 2020 at 09:44:25AM -0800, Diane Trout wrote:
> Could we add a note to tracker or excuses for non-free packages on what
> the developer needs to do to get it to migrate?
IMHO, that's inappropriate. That would mean artificially adding into
britney something that is really a nuance o
On Wed, 2020-12-09 at 18:27 +0100, Mattia Rizzolo wrote:
> Because you seem to not be aware of how non-free works. Non-free is
> not
> autobuilt, so when Andreas uploaded 1.59+ds-2 without any binaries
> then
> "cluster3 has no binaries on any arch". Since there are no binaries
> associated with
On Wed, Dec 09, 2020 at 10:17:56AM +0100, Andreas Tille wrote:
> I'd like to point to a discussion on the Debian Med mailing list which
> was caused by a "fails to migrate to testing for too long" bug. I
> fully agree that these bugs should be filed. However, the bugs are
> immediately set to "Do
* Helmut Grohne , 2016-02-03, 06:17:
I see that there is now a lintian check for this issue whcih is great,
and gives us some idea of how big it is:
https://lintian.debian.org/tags/old-style-config-script-multiarch-path.html
So that lists 240 packages which are MA:same and also contain an
arch
On 03.02.2016 06:34, Helmut Grohne wrote:
Hi Tollef,
On Wed, Feb 03, 2016 at 06:10:50AM +0100, Tollef Fog Heen wrote:
Those scripts can wrap pkg-config, and pkg-config already knows how to
provide user-defined variables, so this sounds like a problem that's
solveable.
What sounds obvious isn'
Hi Tollef,
On Wed, Feb 03, 2016 at 06:10:50AM +0100, Tollef Fog Heen wrote:
> Those scripts can wrap pkg-config, and pkg-config already knows how to
> provide user-defined variables, so this sounds like a problem that's
> solveable.
What sounds obvious isn't. The important bit here is which archi
Hi Wookey,
On Wed, Feb 03, 2016 at 02:49:07AM +, Wookey wrote:
> I see that there is now a lintian check for this issue whcih is great,
> and gives us some idea of how big it is:
> https://lintian.debian.org/tags/old-style-config-script-multiarch-path.html
>
> So that lists 240 packages which
]] Wookey
> A second part of this problem is that foo-config scrips sometimes do
> more than pkg-config does. They are used to supply other information
> about the build environment. I understand that xapian is an example of
> this.
Those scripts can wrap pkg-config, and pkg-config already knows
+++ Johannes Schauer [2016-01-31 15:27 +0100]:
> Quoting Stephen Kitt (2016-01-31 11:49:32)
> > For example, hhvm can't be cross-compiled because it
> > build-depends, directly and indirectly (via imagemagick), on
> > libfreetype6-dev
> > (which contains /usr/bin/freetype-config and is therefore n
* Johannes Schauer , 2016-01-31, 15:27:
libmagickcore-dev is multiarch:foreign
This is surely a bug.
libmagickcore-dev is a transitional package for libmagickcore-6.q16-dev,
which is MA:same, so its interfaces are very much architecture
dependent.
--
Jakub Wilk
Hi Stephen and Bastien,
Quoting Stephen Kitt (2016-01-31 11:49:32)
> I'll give it a shot... (And add this later to the wiki.)
which page will you be editing?
> As I understand it, the page lists *dependency* problems which prevent:
It is indeed important to stress that these are only dependency
Hi Johannes, hi Bastien,
On Sun, 31 Jan 2016 01:53:34 +0100, Johannes Schauer wrote:
> Quoting Bastien ROUCARIES (2016-01-31 00:49:14)
> > Could you document on wiki how can we begin as a package manager. For
> > instance I could not achieve to parse
> > http://bootstrap.debian.net/cross_all/imag
Am 07.08.2014 12:32, schrieb Anton Zinoviev:
> I have two bugs reported against console-setup about keybord not working
> properly under X Window. In both cases I have asked the reportes to
> provide the file /etc/default/keyboard and in both cases the file was
> correct. Therefore, the bugs
Anton Zinoviev (2014-08-07):
> Hi!
>
> I have two bugs reported against console-setup about keybord not working
> properly under X Window. In both cases I have asked the reportes to
> provide the file /etc/default/keyboard and in both cases the file was
> correct. Therefore, the bugs are not
On Tue, 15 Apr 2014, Dmitry Smirnov wrote:
> On Mon, 14 Apr 2014 15:40:00 Thorsten Glaser wrote:
> > • even if I disagree with maintainers (things like bugs
> > in mc), I can mostly live with it (although, when I was
> > m68k porter, some pissed me *seriously* off)
[…]
> I see that all bugs in
On Mon, 14 Apr 2014 15:40:00 Thorsten Glaser wrote:
> • even if I disagree with maintainers (things like bugs
> in mc), I can mostly live with it (although, when I was
> m68k porter, some pissed me *seriously* off)
Easy mate, I'm the only active MC maintainer and we had no disagreement
regard
Hello Andrei and all,
On Fri, 26 Oct 2012 16:24:59 +0300, Andrei POPESCU wrote:
> The discussion about ITO made me think: wouldn't it make more sense to
> also have RFH, RFA, and O filled against the package itself and not
> wnpp? One has to be quite familiar with Debian to check wnpp for RFH,
On Fri, 26 Oct 2012, Andrei POPESCU wrote:
> An immediate solution would probably be to 'affects ' so
> the bugs at least shows up on the package's bug page. Maybe the BTS
> could/should do this automatically?
Doing affects automatically isn't really something that the BTS itself
should do,[1] but
On Fri, Oct 26, 2012 at 03:38:03PM +0200, Thibaut Paumard wrote:
> Le 26/10/2012 15:24, Andrei POPESCU a écrit :
> > The discussion about ITO made me think: wouldn't it make more sense
> > to also have RFH, RFA, and O filled against the package itself and
> > not wnpp? One has to be quite familiar
On Fri, Oct 26, 2012 at 07:39:52PM +0300, Andrei POPESCU wrote:
> On Vi, 26 oct 12, 15:38:03, Thibaut Paumard wrote:
> >
> > it is currently showed in the PTS: e.g.
> > http://packages.qa.debian.org/a/alevt.html:
> > "problems
>
> How many non-DDs/DMs do you think are aware of the PTS? My guess i
On Vi, 26 oct 12, 15:38:03, Thibaut Paumard wrote:
>
> it is currently showed in the PTS: e.g.
> http://packages.qa.debian.org/a/alevt.html:
> "problems
How many non-DDs/DMs do you think are aware of the PTS? My guess is: not
that many. IMVHO the BTS is much more visible, especially to users who
* Thibaut Paumard [121026 15:54]:
> I don't see a reason to move it away from wnpp: its great to have a
> central place for that information, but I agree it is useful to have
> the info forwarded to other places (such as the PTS, and perhaps the
> package's own bug page).
Having a central page to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Le 26/10/2012 15:24, Andrei POPESCU a écrit :
> Hi all,
>
> The discussion about ITO made me think: wouldn't it make more sense
> to also have RFH, RFA, and O filled against the package itself and
> not wnpp? One has to be quite familiar with Debian
On Mon, 2012-08-20 at 13:08 +0200, Bjørn Mork wrote:
> Debian need *both*, and any efforts in this area should be put into
> making them interoperate.
That's my point! :-)
So for the curious amongst you... I've opened the following
ifupdown-plugin related bugs/improvement-ideas upstream:
https://b
2012/4/3 Gergely Nagy :
>> Why do these bugs loose that link to their source package? Have they
>> been gone so long the package isn't even in old-stable anymore and the
>> BTS doesn't record the source package anywhere?
>
> Pretty much, yes.
Also happens that the source package generates several
* Gergely Nagy , 2012-04-01, 13:02:
1) In general, what should the maintainers do to prevent such cases? I
guess that one could reassign the bugs from the old package to the new
one, but it seems obvious that this can be oversought easily,
especially for libpackages where SOVERSION changes ofte
Goswin von Brederlow writes:
> Gergely Nagy writes:
>
>> "Manuel A. Fernandez Montecelo" writes:
>>
>>> So I have several related questions:
>>>
>>> 1) In general, what should the maintainers do to prevent such cases?
>>> I guess that one could reassign the bugs from the old package to the
>>>
Gergely Nagy writes:
> "Manuel A. Fernandez Montecelo" writes:
>
>> So I have several related questions:
>>
>> 1) In general, what should the maintainers do to prevent such cases?
>> I guess that one could reassign the bugs from the old package to the
>> new one, but it seems obvious that this c
2012/4/1 Gergely Nagy :
>> 2) What to do now with all of these bug reports? Reassign them to the
>> related source package in unstable? Contact QA? Nothing at all?
>
> The best course of action would be to check whether the reported issue
> is still valid, and reassign to the appropriate (source)
"Manuel A. Fernandez Montecelo" writes:
> So I have several related questions:
>
> 1) In general, what should the maintainers do to prevent such cases?
> I guess that one could reassign the bugs from the old package to the
> new one, but it seems obvious that this can be oversought easily,
> espe
Ideally the BTS would have a better way (probably involving the
version trees) to associate these bugs with source and or binary
packages still in the archive. Where it couldn't do that the usual
auto-archiving (but not closing since the package could be
reintroduced) would be appropriate. This wou
>> - from maintainers POV, would you accept that?
>
> I've heard from very few people that would actually dislike it, but it
> would be the right way to go in so many senses.
The bugreport against the backported package at least needs to be
copied to whoever did the backport, which complicates th
Hey again,
* Mehdi Dogguy [2011-06-07 17:41:57 CEST]:
> Yes. But, one can still check and remove those tags when appropriate.
> My approach was just to avoid as much as possible to send false bugreports
> to the usual maintainer. The reporter can remove those tags if he's sure
> that it also a
On 07/06/2011 17:35, Gerfried Fuchs wrote:
>
> I think you misinterpret these release tags:
No.
> Setting them on a bug means that the bug affects only that specific
> release. It happens though quite regularly that bugs in backports
> aren't backport specific but also affect testing/unstable, a
Hey,
* Mehdi Dogguy [2011-06-07 17:02:50 CEST]:
> For now users of packages from BPO have to send a mail to
> debian-backports mailing-list, according to [1]. I don't know how you
> handle those bugs, but they seem very easy to miss (even if d-b@l.d.o
> isn't a high traffic list).
This is co
I like this idea and also think that bugs reported against backports
package versions could be automatically directed towards the
backporter instead of the maintainer. First bugs.debian.org would have
to learn about backports package versions.
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To
On Tue, Jun 7, 2011 at 17:02:50 +0200, Mehdi Dogguy wrote:
> >From a maintainer point of view, this could mean more burden. But, if ever
> implemented, debbugs can send a copy of the bugreport to the backporter
> only, and avoid sending it to the usual maintainer of the package.
>
That was discu
Rene Engelhard schrieb am Thursday, den 09. September 2010:
> On Wed, Sep 08, 2010 at 01:22:24PM -0700, Don Armstrong wrote:
> > 1: It's certainly a bug in the backported package using debhelper
> > improperly; it may also be an additional wishlist bug in debhelper.
>
> I disagree, the backported
On Wed, Sep 08, 2010 at 01:22:24PM -0700, Don Armstrong wrote:
> 1: It's certainly a bug in the backported package using debhelper
> improperly; it may also be an additional wishlist bug in debhelper.
I disagree, the backported package uses debhelper correctly. Especially
if you don't use the back
On Wed, 08 Sep 2010, Rene Engelhard wrote:
> On Wed, Sep 08, 2010 at 12:04:24PM -0700, Don Armstrong wrote:
> > That's not a bug in debhelper; it's a bug in the backport of the
> > package, so it shouldn't be filed against debhelper. [Though, perhaps
> > it could be a wishlist request; I don't know
On Wed, Sep 08, 2010 at 12:04:24PM -0700, Don Armstrong wrote:
> That's not a bug in debhelper; it's a bug in the backport of the
> package, so it shouldn't be filed against debhelper. [Though, perhaps
> it could be a wishlist request; I don't know.]
No, it's a bug in the debhelper backport.
If b
On Wed, 08 Sep 2010, Rene Engelhard wrote:
> That would equally make "all bpo bugs go to the BTS" in my case. Thanks, but
> no,
> thanks. Especially not if the "bug" is caused by a external package and/or
> debhelper
> backported but its scripts not adapted back to lenny so that e.g. the built
>
Hi,
On Tue, Sep 07, 2010 at 02:09:24PM -0700, Russ Allbery wrote:
> Steve Langasek writes:
>
> > For the package in question, the backports are done by a fellow
> > comaintainer, so I'm not complaining about the bug traffic; but that
> > doesn't mean it's *right* for that traffic to be going to
Quoting Steve Langasek (vor...@debian.org):
> A single package I'm comaintainer of that has a backports.org backport has
> received at least 12 bug reports to the BTS over the past year referencing
> bpo versions (not counting any that might have been retargeted using
> found/notfound after being
On Tue, Sep 07, 2010 at 12:46:12PM -0700, Don Armstrong wrote:
> On Tue, 07 Sep 2010, Steve Langasek wrote:
> > But when someone takes my package and uploads it somewhere other
> > than the main Debian archive, they incur *all* the responsibilities
> > of maintaining that package, including the res
On Tue, Sep 07, 2010 at 08:57:56PM -0400, Michael Gilbert wrote:
> On Tue, 7 Sep 2010 15:03:56 -0700 Steve Langasek wrote:
> > On Tue, Sep 07, 2010 at 05:13:14PM -0400, Michael Gilbert wrote:
> > > > > Backports has now been declared "officially" supported by the project
> > > > > as a whole. Tha
On Tue, 07 Sep 2010, Sebastian Harl wrote:
> Just to make that clear: I did not talk about any burden for the
> package maintainers but the burden for the BTS
> maintainers/developers to add support for bpo. Whether or not the
> infrastructure for that (in the BTS) might be useful nonetheless is
>
On Tue, 7 Sep 2010 15:03:56 -0700 Steve Langasek wrote:
> On Tue, Sep 07, 2010 at 05:13:14PM -0400, Michael Gilbert wrote:
> > > > Backports has now been declared "officially" supported by the project
> > > > as a whole. That made it the collective responsibility of all
> > > > Debian Developers
On Tue, Sep 07, 2010 at 05:13:14PM -0400, Michael Gilbert wrote:
> > > Backports has now been declared "officially" supported by the project
> > > as a whole. That made it the collective responsibility of all
> > > Debian Developers whether or not individuals in particular like it or
> > > not.
>
Michael Gilbert writes:
> Doing a quick look at the backports mailing list archive, there are less
> than 10 bugs reported per month on average. That is for hundreds of
> packages. Doing some fuzzy math, if you have a package that got
> backported, you may see an additional 10/100 = 0.1 bug repor
On Tue, 7 Sep 2010 13:48:09 -0700, Steve Langasek wrote:
> On Tue, Sep 07, 2010 at 04:18:48PM -0400, Michael Gilbert wrote:
> > Doing a quick look at the backports mailing list archive, there are less
> > than 10 bugs reported per month on average. That is for hundreds of
> > packages. Doing some
Steve Langasek writes:
> For the package in question, the backports are done by a fellow
> comaintainer, so I'm not complaining about the bug traffic; but that
> doesn't mean it's *right* for that traffic to be going to the BTS by
> default.
I wonder if we could apply some logic such as if the b
On Tue, Sep 07, 2010 at 04:18:48PM -0400, Michael Gilbert wrote:
> Doing a quick look at the backports mailing list archive, there are less
> than 10 bugs reported per month on average. That is for hundreds of
> packages. Doing some fuzzy math, if you have a package that got
> backported, you may
On Tue, 7 Sep 2010 22:27:47 +0200, Sebastian Harl wrote:
> Hi,
>
> On Tue, Sep 07, 2010 at 04:18:48PM -0400, Michael Gilbert wrote:
> > On Tue, 7 Sep 2010 21:56:21 +0200, Sebastian Harl wrote:
> > > On Tue, Sep 07, 2010 at 12:46:12PM -0700, Don Armstrong wrote:
> > > > An alternative solution is t
Hi,
On Tue, Sep 07, 2010 at 04:18:48PM -0400, Michael Gilbert wrote:
> On Tue, 7 Sep 2010 21:56:21 +0200, Sebastian Harl wrote:
> > On Tue, Sep 07, 2010 at 12:46:12PM -0700, Don Armstrong wrote:
> > > An alternative solution is to just have reportbug mail the backport
> > > bug reporting mailing l
On Tue, 7 Sep 2010 21:56:21 +0200, Sebastian Harl wrote:
> Hi,
>
> On Tue, Sep 07, 2010 at 12:46:12PM -0700, Don Armstrong wrote:
> > An alternative solution is to just have reportbug mail the backport
> > bug reporting mailing list, and have people bounce messages as
> > appropriate to the BTS.
>
Hi,
On Tue, Sep 07, 2010 at 12:46:12PM -0700, Don Armstrong wrote:
> An alternative solution is to just have reportbug mail the backport
> bug reporting mailing list, and have people bounce messages as
> appropriate to the BTS.
Imho, this is the most sensible approach for now. The number of bugs
[EMAIL PROTECTED] writes:
> To reiterate what I just said in a reply, as it is somewhat important. I
> believe some bugs are being missed in the less used packages. I have
> found several already since I began working on my Deb-Ice project. I
> assume that since the packages are not getting as muc
On Monday 30 July 2007 00:15, Pierre Habouzit wrote:
> On Sun, Jul 29, 2007 at 05:09:11PM -0500, John Goerzen wrote:
> > If you go to http://bugs.debian.org/hpodder, you will see under the
> > outstanding bugs section, several bugs that have been closed for some
> > time. These bugs remain closed (
On Mon, Jul 30, 2007 at 12:15:47AM +0200, Pierre Habouzit wrote:
> thank hurd-i386 for this. (or any arch where your package does not
> build). I wish the bts would ignore non RC archs by default :|
Just for the record, bugscan (and by extension these days, britney) ignores
non-RC archs.
/* St
John Goerzen wrote:
> I am perplexed by this.
>
> If you go to http://bugs.debian.org/hpodder, you will see under the
> outstanding bugs section, several bugs that have been closed for some time.
> These bugs remain closed (were not reopened), the BTS page for each bug
> knows about that, yet
On Sun, Jul 29, 2007 at 05:09:11PM -0500, John Goerzen wrote:
> Hi,
>
> I am perplexed by this.
>
> If you go to http://bugs.debian.org/hpodder, you will see under the
> outstanding bugs section, several bugs that have been closed for some time.
> These bugs remain closed (were not reopened),
On Fri, Jan 26, 2007 at 01:13:00PM +0100, Wouter Verhelst wrote:
> On Sat, Jan 20, 2007 at 02:13:37PM +, Ross Burton wrote:
> > If you have any particular pet features that have been removed in GNOME
> > and you can make a valid case for their re-inclusion, then file a bug.
>
> I'm afraid the
On ven, 2007-01-26 at 14:13 -0500, Greg Folkert wrote:
> I use GNOME because it SUKCETH TEH LEASTEST.
>
> KDE is far worse, IMO.
because it offers more than one way to do things?
--
Yves-Alexis
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [E
On Fri, 2007-01-26 at 20:02 +0100, Mike Hommey wrote:
> On Fri, Jan 26, 2007 at 12:48:47PM -0500, Greg Folkert <[EMAIL PROTECTED]>
> wrote:
> > On Fri, 2007-01-26 at 15:15 +0100, Josselin Mouette wrote:
> > > For programming languages, I prefer the one that makes programmers
> > > easily understan
On Fri, Jan 26, 2007 at 12:48:47PM -0500, Greg Folkert <[EMAIL PROTECTED]>
wrote:
> On Fri, 2007-01-26 at 15:15 +0100, Josselin Mouette wrote:
> > For programming languages, I prefer the one that makes programmers
> > easily understand all code written by others. For desktop environments,
> > I pr
On Fri, 2007-01-26 at 15:15 +0100, Josselin Mouette wrote:
> For programming languages, I prefer the one that makes programmers
> easily understand all code written by others. For desktop environments,
> I prefer the one that provides the cleanest and most efficient UI. YMMV.
Wow, my extreme GNOME
Le vendredi 26 janvier 2007 à 13:19 +0100, Wouter Verhelst a écrit :
> On Sat, Jan 20, 2007 at 02:21:17PM +0100, Josselin Mouette wrote:
> > Why do you assume it? The usability processes in GNOME imply, on the
> > contrary, that there is a good way to achieve every use case.
>
> Thank you for this
Twas brillig at 13:19:36 26.01.2007 UTC+01 when Wouter Verhelst did gyre and
gimble:
WV> There most be a GNOME motto, and it says "TSBOOWTDI": There
WV> Should Be Only One Way To Do It.
Actually, it's already the Python motto ;)
--
JID: [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAI
On Sat, Jan 20, 2007 at 02:21:17PM +0100, Josselin Mouette wrote:
> Why do you assume it? The usability processes in GNOME imply, on the
> contrary, that there is a good way to achieve every use case.
Thank you for this insight.
There is a Perl motto, and it says "TIMTOWTDI": There Is More Than O
On Sat, Jan 20, 2007 at 02:13:37PM +, Ross Burton wrote:
> If you have any particular pet features that have been removed in GNOME
> and you can make a valid case for their re-inclusion, then file a bug.
I'm afraid the GNOME bugzilla can't handle that amount of bugs.
--
Home is where you ha
On Mon, 2007-01-22 at 19:32 +0100, Josselin Mouette wrote:
> Oh, right. Now, you're blaming GNOME for the way Christian Marillat used
> to deal with bugs. Fine.
I bow GNOME Overlord.
> People who use the software and report bugs when they find some are more
> likely to get support than those bash
On Monday 22 January 2007 18:05, Josselin Mouette wrote:
> Le lundi 22 janvier 2007 à 16:44 +0100, cobaco (aka Bart Cornelis) a
> écrit :
> > Those capplets were wanted enough to have been made, so obviously they
> > scratch someones itch. Or in other words they're usefull to someone
> > even if th
Le lundi 22 janvier 2007 à 13:10 -0500, Greg Folkert a écrit :
> I am telling you right now, that the BUGS of which I experience, I
> "discover" the bugs in bugs.d.o. Exactly the same problems...
> workarounds offered by the developers are typically non-existent and
> typically are tagged "not repr
On Mon, 2007-01-22 at 17:30 +0100, Josselin Mouette wrote:
> Le lundi 22 janvier 2007 à 09:59 -0500, Greg Folkert a écrit :
> > Yeap, you are right. I am dumb.
>
> I was not sure of it, but this mail just convinced me you are.
>
> > But let me ask you this, are you telling me that I need to spend
Le lundi 22 janvier 2007 à 16:44 +0100, cobaco (aka Bart Cornelis) a
écrit :
> Those capplets were wanted enough to have been made, so obviously they
> scratch someones itch. Or in other words they're usefull to someone even if
> they're not usefull to you personally.
Oh, really?
Do you often n
Le lundi 22 janvier 2007 à 09:59 -0500, Greg Folkert a écrit :
> Yeap, you are right. I am dumb.
I was not sure of it, but this mail just convinced me you are.
> But let me ask you this, are you telling me that I need to spend *MUCH*
> more time to fix the settings than to remove them and reconst
On Monday 22 January 2007 15:08, Josselin Mouette wrote:
> While it is completely useless bloat for capplets (or at least, it would
> if capplets were merged appropriately and useless ones were removed), I
> hope it will be used for panel applets insertion.
Those capplets were wanted enough to ha
On Mon, 2007-01-22 at 15:12 +0100, Josselin Mouette wrote:
> Le samedi 20 janvier 2007 à 21:32 -0500, Greg Folkert a écrit :
> > I have regularly had my GCONF stuff partially corrupted in any case.
> > Associations go away, programs crash spontaneously, I look for bugs...
> > find the exact same th
Le samedi 20 janvier 2007 à 21:32 -0500, Greg Folkert a écrit :
> I have regularly had my GCONF stuff partially corrupted in any case.
> Associations go away, programs crash spontaneously, I look for bugs...
> find the exact same things I have. Solution or workaround? remove *ALL*
> user gconf and
Le dimanche 21 janvier 2007 à 12:46 -0300, Margarita Manterola a écrit :
> Hi!
>
> On 1/20/07, Josselin Mouette <[EMAIL PROTECTED]> wrote:
> > There is still work to do, e.g. by
> > looking at the insane list of capplets.
>
> If you are referring to the gnome-panel applets.
No, I'm talking about
On Sun, 2007-01-21 at 18:06 +0100, David Weinehall wrote:
> On Sat, Jan 20, 2007 at 09:32:07PM -0500, Greg Folkert wrote:
> > On Sat, 2007-01-20 at 21:16 +0100, David Weinehall wrote:
> > > On Sat, Jan 20, 2007 at 06:34:18AM -0500, Greg Folkert wrote:
> > > > On Sat, 2007-01-20 at 11:51 +0100, Jos
On Sat, Jan 20, 2007 at 09:32:07PM -0500, Greg Folkert wrote:
> On Sat, 2007-01-20 at 21:16 +0100, David Weinehall wrote:
> > On Sat, Jan 20, 2007 at 06:34:18AM -0500, Greg Folkert wrote:
> > > On Sat, 2007-01-20 at 11:51 +0100, Josselin Mouette wrote:
> > > > Le samedi 20 janvier 2007 à 04:30 -05
Hi!
On 1/20/07, Josselin Mouette <[EMAIL PROTECTED]> wrote:
There is still work to do, e.g. by
looking at the insane list of capplets.
If you are referring to the gnome-panel applets. May I remind you
that this list used to be organized in menues, with lines of the same
size of items in the A
asier to find an item in a short menu"
> > | \
> > mail -s "Re: Bugs in default GNOME etch?"
> > [EMAIL PROTECTED]
> > echo "everyone else: it's impossible to find an item that isn't
> > there" | \
> > mail -s "Re: Bugs in defa
On dim, 2007-01-21 at 12:31 +, Stephen Gran wrote:
> This could quickly get recursive. Let me save you the trouble:
>
> while true; do
> echo "kool-aid drinker: it's easier to find an item in a short menu"
> | \
> mail -s "Re: Bugs in default GNO
27;s easier to find an item in a short menu than in a long menu that
> is cluttered by useless stuff.
This could quickly get recursive. Let me save you the trouble:
while true; do
echo "kool-aid drinker: it's easier to find an item in a short menu" | \
mail -s "R
On Sun, Jan 21, 2007 at 02:30:46AM -0800, Steve Langasek <[EMAIL PROTECTED]>
wrote:
> On Wed, Jan 17, 2007 at 11:45:32AM +, Sebastian Heinlein wrote:
> > You have also to take a look how efficient a way is. Finding a menu entry
> > in a
> > long list is quite ineffcient (Fitts' law). Compare
On Wed, Jan 17, 2007 at 11:45:32AM +, Sebastian Heinlein wrote:
> You have also to take a look how efficient a way is. Finding a menu entry
> in a
> long list is quite ineffcient (Fitts' law). Compare the two menus in
> Debian and
> Ubuntu.
It's infinitely easier to find an item in a long men
On Sat, 2007-01-20 at 21:16 +0100, David Weinehall wrote:
> On Sat, Jan 20, 2007 at 06:34:18AM -0500, Greg Folkert wrote:
> > On Sat, 2007-01-20 at 11:51 +0100, Josselin Mouette wrote:
> > > Le samedi 20 janvier 2007 à 04:30 -0500, Greg Folkert a écrit :
> > > > I would assert they are not listeni
This one time, at band camp, David Weinehall said:
> On Sat, Jan 20, 2007 at 06:34:18AM -0500, Greg Folkert wrote:
> > It I have to use some archaic command
> > like (btw I don't really mind them *IF* they are well documented) but
> > like:
> > gconftool-2.3-1-9.mark32 -a2 -r4 --/usr/sbin/s
Hello!
On Tue, 16 Jan 2007 10:48:03 +0100, Loïc Minier wrote:
> On Tue, Jan 16, 2007, Luca Capello wrote:
>> first of all, I posted to d-d because I think the problem is not
>> restricted to GNOME, but if I'm wrong, please continue this
>> discussion to debian-gtk-gnome (which I cc:ed) and cc: me
Le samedi 20 janvier 2007 à 15:21 +0100, cobaco (aka Bart Cornelis) a
écrit :
> So Gnome has obviously not 'removed tons of features' (your words), they've
> instead consolidated features, replacing multiple features with single
> better features all over the place?
> And I suppose the mountains
On Sat, Jan 20, 2007 at 06:34:18AM -0500, Greg Folkert wrote:
> On Sat, 2007-01-20 at 11:51 +0100, Josselin Mouette wrote:
> > Le samedi 20 janvier 2007 à 04:30 -0500, Greg Folkert a écrit :
> > > I would assert they are not listening to their former BIGGEST fans and
> > > users. You can easily fin
On Saturday 20 January 2007 14:21, Josselin Mouette wrote:
> Le samedi 20 janvier 2007 à 13:34 +0100, cobaco (aka Bart Cornelis) a
> > IMHO that just means those usability engineers took the easy way out of
> > a scaling problem: instead of adressing the actual problem, they just
> > made sure they
On Sat, 2007-01-20 at 14:13 +, Ross Burton wrote:
> On Sat, 2007-01-20 at 06:34 -0500, Greg Folkert wrote:
> > Are you telling me that these features I keep see getting removed are
> > *NOT* about usability for me? OK, functionality to me... Functionality
> > for me determines my usability. It
On Sat, 2007-01-20 at 06:34 -0500, Greg Folkert wrote:
> Are you telling me that these features I keep see getting removed are
> *NOT* about usability for me? OK, functionality to me... Functionality
> for me determines my usability. It I have to use some archaic command
> like (btw I don't really
Le samedi 20 janvier 2007 à 13:34 +0100, cobaco (aka Bart Cornelis) a
écrit :
> By taking out features you decrease the number of goals you can use the
> software for. If you can't use the software for a certain goal at all then
> it's less usable for that goal then a package with an interface fr
On Saturday 20 January 2007 11:51, Josselin Mouette wrote:
> Le samedi 20 janvier 2007 à 04:30 -0500, Greg Folkert a écrit :
> > I would assert they are not listening to their former BIGGEST fans and
> > users. You can easily find droves rants/discussions of current GNOME
> > users very disgruntled
1 - 100 of 285 matches
Mail list logo
