Quoting Moritz Muehlenhoff (j...@inutil.org):
> Eight months later we're now in the jessie cycle. Can we drop menu from
> the desktop task now?
Sure! I simply completely forgot about that item..:-)
I just committed a fix that drops menu from task-desktop and menu-xdg
from task-kde-desktop.
And
Quoting Russ Allbery (r...@debian.org):
> At the time, we therefore decided that this was some distance away from
> being widely used enough to put in common-licenses, given the various
> drawbacks of that (adding a level of indirection for people reviewing
> licenses and so on).
>
> Do you think
Quoting Dmitry E. Oboukhov (un...@debian.org):
> PW> As an example of the practical effects of flags in the context of
> PW> Debian; a number of years ago we lost our kernel maintainer, partially
> PW> because KDE in Debian included a flag of a country the maintainer (and
> PW> his government) dis
Quoting Dmitry E. Oboukhov (un...@debian.org):
> There are many packages in debian contain flag images.
I think this whole thread answeredsomething that wasn't asked in
your question (is is good or bad to use flags). Flags *are* used,
whether we like it or not...or whether this is a good idea
Quoting Cyril Brulebois (k...@debian.org):
> > http://dep.debian.net/deps/dep4/#index7h2
> > "During the transition, those bugs will remain. After the transition,
> > those bugs will go away so there should be no need for a closure
> > method. We’ll need to rely on i18n.debian.org for translation
Quoting Bill Allombert ([EMAIL PROTECTED]):
> > That latter part probably belongs more to the Developer's
> > Reference. Indeed, a section about po4a and a simple way to setup a
> > framework for localized manpages would be a great addition to it.
>
> Frankly, I do not like po4a for manpages. I t
Quoting Helge Kreutzmann ([EMAIL PROTECTED]):
> +If a loclized man page for a certain command is provided, it should
s/loclized/localized
> +either be up to date or it should be clearly visible that this version
> +is outdated (either by a note in the beginning or by showing the
> +
Quoting Russ Allbery ([EMAIL PROTECTED]):
> > Thanks for your feedback!
>
> Hm, in that case, you shouldn't call it "Time Tracking" if you want gtimer
Hmmm, is "Tracking" really needed ?
Or would "Applications/Time" just be enoughbut maybe too vague and
therefore attracting thigns that are
(resending that mail that apparently never made it to its recipients)
Quoting Colin Watson ([EMAIL PROTECTED]):
> Christian Perrier seconded this here:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=440420#100
>
> However, since later discussion indicated that we should
(Colin CC'ed in case he's not subscribed to the bug or to the
debian-policy package PTS)
Quoting Russ Allbery ([EMAIL PROTECTED]):
> This proposal and patch looks good to me, although I'd prefer to see a few
> more seconds before I queue it up for applying to Policy 3.7.4.
I can't really make t
Quoting Steve Langasek ([EMAIL PROTECTED]):
> A few years back, Samba upstream began using CUPS as the default printing
> system whenever CUPS support was enabled. At the time, cupsys was Priority:
> optional, and lpr as the standard Unix printing interface was Priority:
> standard (or higher), so
Quoting Manoj Srivastava ([EMAIL PROTECTED]):
> Actually, policy is usually the last thing that you want to
> do, in the general case. Policy is usually stable (well, not quite as
> stable as it has been this year, but work seems to be easing up a
> trifle, so expect a policy release in
> I would really like to see that happening at the beginning of the lenny
> release cycle. Packages that prompt without using debconf make it
> unnecessary difficult to test them using piuparts.
>
> Looking at my piuparts results (testing packages in etch), most packages
> that prompt the user alr
After Anthony Towns suggestion that he believes that a "should" would
be enough, I agree with his arguments.
Here a corrected patch which s/must/should. I will propose the
enforced use of po-debconf as a release goal for Lenny.
--- policy.sgml.old 2006-12-13 22:24:05.534361649 +0100
+++ polic
Package: debian-policy
Version: 3.7.2.2
Severity: wishlist
Tags: patch
This should probably have been done for a long time but better late than
never.
The gettext-based system for debconf templates internationalisation is now
mature enough (it appeared immediately after the release of woody).
Th
> In the mean time, we've made use of debconf to interact with users
> pretty much mandatory, though I'm not currently sure if it is truly
> mandatory. Only a fairly few packages remain that do it without debconf
AFAIK it is not mandatory (IMHO, it shouldI would even suggest
making the use of
> Since there are new dpkg maintainers, I asked them on Thu, 19 Jan 2006,
> what was their opinion on the matter and whether they would accept my
> proposal or yours. So far I did not get any answer.
You probably sent the request a little bit too early. The dpkg
maintenance team was still in the
> "HAM" is not an acronym, so "Ham Radio" would be more appropriate.
>
> Even better (IMHO) is the full term "Amateur Radio", but some may
> disagree. I've CC'd debian-hams for their input also.
HAM is probably well known among the amateur radio community.
However, *outside* this community, th
> The difficult with strings like these, which will appear like this:
>
> msgid "Saving"
>
> msgid "Locking"
>
> msgid "Monitoring"
Thankfully, Bill is very clever about translation issues and it's
about one year since he put very detailed commentd in the POT and PO
files:
#
#. First level e
Quoting Joey Hess ([EMAIL PROTECTED]):
> Seconded once more.
Fourthed (counting Russ second)
signature.asc
Description: Digital signature
> Having looked into this a little more, I now think that simple
> misunderstanding may be why this turned into a major debate. The
> original wishlist said something like, "please have dpkg follow
> policy." Of course, what Thomas meant was, "please copy the style
> mentioned in policy for some
Quoting Chris Waters ([EMAIL PROTECTED]):
> On Mon, Feb 14, 2005 at 11:20:19AM +, [EMAIL PROTECTED] wrote:
>
> > No shenanigans here. The dpkg maintainer says that he wants guidance
> > from policy.
>
> I could say I want guidance from policy on what color of shirt I wear
> to my next LUG me
Quoting Frank Küster ([EMAIL PROTECTED]):
> Package: debian-policy
> Version: 3.6.1.0
> Severity: wishlist
>
> This is not a formal proposal (I currently want to release sarge, not
> discuss policy changes), it's just a reminder that this should be
> dealt with somewhen.
I see at least one occasi
(l10n-french removed from the CC listI did not intend to keep this
discussion thereit still belongs to i18n, imho...)
> I'd like to add one thing to the proposal: there needs to be an
> exemption somehow for packages with high priority, e.g. Essential
> packages and those in the dependenc
Quoting Anthony Towns (aj@azure.humbug.org.au):
> On Fri, Aug 22, 2003 at 07:46:56AM +0200, Christian Perrier wrote:
> > This proposal is what I think to be the next step : make this a "must"
>
> This won't be happening for sarge. If you want it to happen, pleas
Package: debian-policy
Version: 3.6.1
Severity: wishlist
Now that debconf use is recommended in Policy (since 3.6.1), I think it's
time to think about the future.
During the discussion about this amendment (bug #176506), it was decided to
only make this a "should" requirement, which is achieved
Quoting Josip Rodin ([EMAIL PROTECTED]):
> On Thu, Jul 10, 2003 at 06:21:42PM +0200, Christian Perrier wrote:
> > Well, I of course second this proposal, just being tracking down
> > packages who do not use debconf
>
> Speaking of which, I object to the proposal to g
Well, I of course second this proposal, just being tracking down
packages who do not use debconf
There seems to be very few of them, some with quite good reasons for
delaying the change (see #184979 for base-passwd).
At this time, I have found :
anacron (lazy maintainer ?)
base-passwd (good
> I suggest we add the following to policy section 11.4.
> (Wording by Bill Allombert.)
I don't know if a base devel opinion counts (I *know* it does...:-))
but as I use PTS for tracking down policy changes (and keep my
Standards-Version: fiels up-to -date...:-)), I use this way to express
my fee
29 matches
Mail list logo
