-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/24/2015 07:23 PM, Francesco Poli (wintermute) wrote:
> I don't feel too safe to enter personal data on a page that is not
> fully encrypted. I suppose other people feel the same and I wonder why
> this issue has not yet been solved.
The prob
On 02/04/2013 08:40 AM, Giacomo A. Catenazzi wrote:
> On 02/03/2013 10:53 PM, Daniel Baumann wrote:
>> On 02/03/2013 10:44 PM, Cyril Brulebois wrote:
>>> Now please explain how exactly syslinux-themes-debian is involved
>>> here.
>>
>> it's a bug in you
On 02/03/2013 10:53 PM, Daniel Baumann wrote:
> On 02/03/2013 10:44 PM, Cyril Brulebois wrote:
>> Now please explain how exactly syslinux-themes-debian is involved
>> here.
>
> it's a bug in your config, you need more files present on the media, as
> the link to the corresponding commit in live-bu
On 03.09.2010 01:46, Russ Allbery wrote:
Samuel Thibault writes:
Well, it's mostly
- some people saying "it's useless",
- while other people saying "I need it",
and also
- "en_US.UTF-8 is just fine" vs.
- "en_US.UTF-8 sucks, we really need C.UTF-8 instead"
without any convergence.
On 21.08.2010 08:36, Raphael Hertzog wrote:
On Fri, 20 Aug 2010, Russ Allbery wrote:
diff --git a/virtual-package-names-list.txt b/virtual-package-names-list.txt
index 9ba66e5..2308d39 100644
--- a/virtual-package-names-list.txt
+++ b/virtual-package-names-list.txt
@@ -123,6 +123,8 @@ News and M
On 19.08.2010 09:45, Russ Allbery wrote:
"Giacomo A. Catenazzi" writes:
On 18.08.2010 23:38, Russ Allbery wrote:
Julien Cristau writes:
Is there a spec somewhere about the command line arguments for mailx?
I know that bsd-mailx and heirloom-mailx do completely different
thi
On 19.08.2010 09:37, Russ Allbery wrote:
"Giacomo A. Catenazzi" writes:
No, I think it is wrong!
The debian/copyright also include packaging copyright. I think the part
involved in this proposal is for such reasons. So IMHO we must still
require the names of packagers (and th
On 18.08.2010 23:38, Russ Allbery wrote:
Julien Cristau writes:
On Wed, Aug 18, 2010 at 12:31:59 -0700, Russ Allbery wrote:
I propose the following addition. Seconds or objections? (As
mentioned elsewhere in the file, the * indicates that the providing
packages are using alternatives, whic
On 19.08.2010 04:10, Russ Allbery wrote:
Charles Plessy writes:
Information about the initial Debian maintainers partially overlaps the
information in debian/changelog, and the copyright statements for the
packaging work.
Under normal circumstances, it always duplicates information in
debian
On 26.07.2010 15:08, Alexander Reichle-Schmehl wrote:
Hi!
* Giacomo A. Catenazzi [100607 09:29]:
Please update lxr-cvs to the new stable version. The new version 0.9.8 of
lxrng fix several cross-site scripting vulnerabilities (CVE-2009-4497) reported
in bug #575745
The new version was
On 07/15/2010 06:53 PM, Russ Allbery wrote:
"Giacomo A. Catenazzi" writes:
As we have in "test" item, I think we should add ",if implemented as a
shell built-in," also for the kill command.
Good point. Here's a new patch. (This doesn't apply to
On 05.07.2010 01:02, Raphael Geissert wrote:
On Sunday 04 July 2010 00:04:20 Russ Allbery wrote:
Yeah, I was trying too hard to avoid a problem which doesn't really
exist. Here's an updated patch.
diff --git a/policy.sgml b/policy.sgml
index bad28af..8b715d0 100644
--- a/policy.sgml
+++ b/poli
On 04.07.2010 10:42, Kurt Roeckx wrote:
On Sat, Jul 03, 2010 at 12:26:40PM -0700, Russ Allbery wrote:
--- a/policy.sgml
+++ b/policy.sgml
@@ -7225,10 +7225,10 @@ INSTALL = install -s # (or use strip on the files in
debian/tmp)
for C files) will need to be compiled twice, for the nor
On 11.06.2010 14:25, Andrew McMillan wrote:
If the code is v1-or-later then a trivial fork (by the original
developer) is able to relicense it as v2-or-later or v3-or-later. If
the original developer is unhappy with doing that, then they do have
uncommon licensing desires.
It would be illegal
On 11.06.2010 13:16, Andrew McMillan wrote:
On Fri, 2010-06-11 at 11:35 +0200, Santiago Vila wrote:
Ok, I agree that it would a good idea to include GPL-1 in common-licenses
because of the high number of packages still using it.
I'm sorry, but I disagree, for the time being. I do not believe
On 10.06.2010 21:45, Russ Allbery wrote:
I recently did a survey of both licenses already listed in common-licenses
and ones proposed for common-licenses using a Perl script that's now in
the debian-policy Git repository. The result was that the MPL version 1.1
was used by 654 binary packages in
On 05.06.2010 15:00, Xavier Brochard wrote:
Package: lxr-cvs
Version: 0.9.5+cvs20071020-1
Severity: serious
Tags: security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
--- Please enter the report below this line. ---
Please update lxr-cvs to the new stable version. The new version 0
On 04.06.2010 04:40, Andrew McMillan wrote:
On Thu, 2010-06-03 at 18:31 -0700, Russ Allbery wrote:
Charles Plessy writes:
I also like the idea, so I prepared a patch (attached)
Thank you!
RFC 822 dates use only two digits for the years, but Debian changelogs
described by this paragraph (§
On 02.06.2010 14:59, Bill Allombert wrote:
What is the diffrence between RFC5322 and RFC2822 time format ?
RFC 5322 was only released in 2008, so the standard that packages
actually follow is clearly RFC2822.
I would prefer if we keep a reference to RFC2822 because is is
more well known than RF
On 17.03.2010 14:36, Vincent Lefevre wrote:
On 2010-03-17 13:41:04 +0100, Giacomo A. Catenazzi wrote:
On 17.03.2010 11:29, Vincent Lefevre wrote:
On 2010-03-07 16:17:08 +0100, Aurelien Jarno wrote:
On amd64, only sincos has an optimized version,
It may be optimized, but completely buggy
On 17.03.2010 11:29, Vincent Lefevre wrote:
On 2010-03-07 16:17:08 +0100, Aurelien Jarno wrote:
On amd64, only sincos has an optimized version,
It may be optimized, but completely buggy. For instance, on 1e22,
sincos returns 0.46261304076460174617 for the sine instead of
-0.8522008497671887949
On 29.01.2010 12:57, Wesley Schwengle wrote:
Michael Meskes wrote:
severity 567316 normal
thanks
Severity: grave
Justification: renders package unusable
You're kidding right? I just don't get the joke.
A calender which displays incorrect weeks is not usable, not to me at least.
"Package
On 06.01.2010 10:35, Jonathan McDowell wrote:
Please consider applying the attached patch to this package. It changes
the init script to use the logging functions in lsb-base, which allows
for easier customisation of system boot message format. I've also
corrected a couple of spelling mistakes in
Thorsten Glaser wrote:
Albert Cahalan dixit:
Unless plain "C" goes UTF-8
Not going to happen, it’s not binary-safe. (I fought that in
MirBSD with the OPTU-8/16 encoding scheme.)
Why not? Note that usual functions work on bytes, not on characters, and
on POSIX utilities the old/classical op
ACK the patch and the NMU.
Thanks!
I really had to solve myself the bugs (and a lot earlier).
ciao
cate
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hello Mark,
Mark Purcell wrote:
Version: 3.9.8-1
On Sunday 01 November 2009 19:44:47 Giacomo A. Catenazzi wrote:
Hello,
this is a moer general problem:
hp-check check the wrong things (or the package dependencies are
wrong).
hplip now will advise if it is a run time checks or build time
Hello,
this is a moer general problem:
hp-check check the wrong things (or the package dependencies are
wrong).
In this case:
hp-check execute "cups-config --version", but this command is available
only on cups-dev.
On some other dependency checks, hp-check doesn't check for the plain
subsystem
Jakub Wilk wrote:
* Giacomo A. Catenazzi , 2009-10-29, 10:16:
"must" is a quite common word in the Debian Policy:
For consistency, I'd do s/MUST/must/.
But not automatically. On RFC usage "must" is different from "MUST",
so you SHOULD distinguish th
Jakub Wilk wrote:
"must" is a quite common word in the Debian Policy:
For consistency, I'd do s/MUST/must/.
But not automatically. On RFC usage "must" is different from "MUST", so
you SHOULD distinguish the normative "MUST" and with the non normative "must".
And BTW if we do such change, w
Raphael Hertzog wrote:
On Wed, 14 Oct 2009, Russ Allbery wrote:
Do both of our proposed cron daemons support that same syntax? (Does
anyone here use bcron to comment on that?)
bcron supports the */n syntax, but not @reboot and the other @*. See
http://manpages.debian.net/cgi-bin/man.cgi?query
Raphaël Hertzog wrote:
Package: debian-policy
Version: 3.8.3.0
Severity: wishlist
We have some unwritten packaging rules and it would be good to write them
down even if some of them appear to be obvious to most of us. I think in
particular to stuff like:
- a package must at least be upgradable
Yes, thanks you for remind me to publish the new g15daemon.
On removing the *.la files I used a shortcut, but than I forgot
to upload the new version of g15daemon without .la file (and references
to no more existent libg15 la file.
I'll upload the new version of g15daemon in next few days, and
I'
Hajo Möller wrote:
Hello,
update-intel-microcode gets the last mentioned microcode instead of the
lastest one, as the RSS feed currently mentions two firmware files and
sed failing to use non-greedy patterns.
The attached patch uses perl to parse the wget output, there's no need
to add perl-base
Florian Weimer wrote:
* MJ Ray:
cate wrote:
Eugen Dedu wrote:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532456, about licenses
I think there is a problem in terminology. AFAIK (but IANAL), the
"any use" doesn't include distribution of software.
For this reason I think it is safe to cl
Eugen Dedu wrote:
Hi,
We have a bug report,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532456, about licenses
of various plugins of opal package, and I do not know if the licenses
involved are DFSG-free. Could you please tell me if these plugins are
allowed to be in debian main?
The mai
Manoj Srivastava wrote:
Hi,
The most recent version of this proposal was:
--8<---cut here---start->8---
--- virtual-package-names-list.txt~ 2009-03-15 18:19:17.0 +
+++ virtual-package-names-list.txt 2009-03-15 18:20:00.0 +
Russ Allbery wrote:
"Giacomo A. Catenazzi" writes:
Do we really need to use the triplets? Do you see some possible cases
where we must really specify the first part?
Isn't someone working on a klibc port? That would require using the
triplet.
Does the new dpkg support al
Could you check in /var/log/syslog, if at the time of the crash
there is some additional information?
The daemon is terminated with SIGKILL, and this signal should
not be caused by the daemon itself (SEGSEGV, SIGILL, SIGBUS, etc.
are delivered for internal errors).
So I think an external program
Manoj Srivastava wrote:
+
+
+ A package may specify an architecture wildcard. Architecture
+ wildcards are in the format os-any and
+ any-cpu. Internally, the package
+ system normalizes the GNU triplets and the Debian
+ arches into Debian arch
Package: debian-policy
Version: 3.8.3.0
In policy 5.6.16, about Format field I read:
: This field specifies a format revision for the file. The most current format
: described in the Policy Manual is version 1.5. The syntax of the format
: value is the same as that of a package version number e
Could you send also the output of
grep g15daemon /var/log/syslog
thanks
cate
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Xavier Bestel wrote:
Package: microcode.ctl
> Version: 1.17-12
> Severity: serious
> Justification: Policy 2.5
your package depends on "makedev" which is an "extra" packages. That's a
violation of Debian
Policy 2.5: "Packages must not depend on packages with lower priority values
(excluding
pancho horrillo wrote:
> When I run mplayer, or openarena, somehow udev reacts as if the device
> (Z-10 USB speakers) was reconnected, and calls
strange. On my system I don't see such things (with vlc and mplayer).
udev rules are still an hack, because I had not yet time to correct
the g15daemon
Ritesh Raj Sarraf wrote:
Just for the record, apt-offline is being tailored for inclusion into Debian at:
http://git.debian.org/?p=users/rrs-guest/apt-offline.git;a=summary
Hello,
I find interesting your program.
I'm one of the maintainers of apt-zip, which do similar tasks, but:
- it is not
Petter Reinholdtsen wrote:
I just tried to install the g15daemon package on a Dell Latitude D505,
and there the package failed to install because the init.d script
return an error exit code (1). The messages sent to syslog indicate
that the daemon failed to start because the supported hardware w
It should be easy to include support for aspell.
Really using "spell -i /usr/bin/aspell" works as expected,
using aspell instead of spell.
But this should be done by default: if ispell doesn't exists,
the program should try aspell.
ciao
cate
--
To UNSUBSCRIBE, email to debian-bugs-di
The new kernels support also other architectures.
From latest kernel sources:
arch/powerpc/Kconfig:config HAVE_LATENCYTOP_SUPPORT
arch/sparc/Kconfig:config HAVE_LATENCYTOP_SUPPORT
arch/arm/Kconfig:config HAVE_LATENCYTOP_SUPPORT
arch/sh/Kconfig:config HAVE_LATENCYTOP_SUPPORT
arch/s390/Kconfig:con
Frans Pop wrote:
This oneliner change would fix the issue as well:
+++ b/packages/base-installer/debian/bootstrap-base.postinst
@@ -88,7 +88,7 @@ install_base_system () {
# so make a backup to be restored later
copied_fstab=true
cp /target/etc/fsta
Aníbal Monsalve Salazar wrote:
Package: wnpp
Severity: wishlist
Owner: Anibal Monsalve Salazar
* Package name: libposix
I still have doubts that this package is undistributable with this name,
because of POSIX trademark (but DFSG allow us to change the package name).
Note: It is not the
Ben Pfaff wrote:
Russ Allbery writes:
Ben Finney writes:
If you're going that far, please perform one of the following:
s/rounded/fractions rounded up/
s/rounded/fractions rounded down/
s/rounded/fractions rounded to the nearest whole number/
to disambiguate the calculation.
D
Don Armstrong wrote:
On Wed, 17 Jun 2009, Sune Vuorela wrote:
so it seems that the "alternative" interpretation, is that "if there
is a interface, then it must be used", but all that is wrapped in a
"should", which is not as binding as a "must".
While this section of policy could probably be c
Raphael Hertzog wrote:
For the second argument:
[ using bash ]
$ type printf
printf is a shell builtin
$ dash
$ type printf
printf is a shell builtin
There's no external executable needed.
but also "echo -n" is recognized by these tools.
I've interpreted the original bug report as a way to a
Filippo Rusconi wrote:
On Mon, May 11, 2009 at 02:11:18PM +0200, Julien Cristau wrote:
On Mon, May 11, 2009 at 13:46:30 +0200, Lionel Elie Mamane wrote:
No, policy is very clear on that: if you call the "build" target, you
_must_ satisfy Build-Depends-Indep and Build-Conflicts-Indep:
And pol
martin f krafft wrote:
[moving debian-rele...@l.d.o to Bcc, continuing discussion in bug log]
also sprach Andreas Metzler [2009.05.04.1856
+0200]:
FWIW as previously discussed on debian-devel starting with the
lastest upload (4.69-10) exim4-daemon-light provides default-mta.
Excellent. If t
Thorsten Glaser wrote:
Giacomo A. Catenazzi dixit:
a real locale), but in this case I would also test some UTF-16
or Asian locale (mksh should not assume UTF-8 in these cases).
It doesn’t. This test is already run for the C locale.
Besides, there are no UTF-16 or somesuch locales on UNIX®
Thorsten Glaser wrote:
Giacomo A. Catenazzi dixit:
I think you misunderstand the mksh part of the problem.
mksh has two modi: a legacy mode, in which it does not make any
assumptions about charsets or encodings and is 8-bit clean and
mostly 8-bit transparent, safe a few mostly past bugs and
Andrew McMillan wrote:
On Wed, 2009-04-08 at 10:15 +0200, Giacomo A. Catenazzi wrote:
So I've a question: what does UTF-8 mean in this context (C.UTF-8) ?
It is not a stupid question, and the answer is not the UTF-8 algorithm
to code/decode unicode.
I'm still thinking that you are
Ok, maybe I found the problem.
Giacomo A. Catenazzi wrote:
> No ;-) Ok, it take me some modifications of your program and
looking to POSIX to discover the reason.
You forget to check error codes. In this case we have
"Invalid or incomplete multibyte or wide character" in the
non
Roger Leigh wrote:
On Tue, Apr 07, 2009 at 10:36:20AM +0200, Giacomo A. Catenazzi wrote:
>> Roger Leigh wrote:
I can't help but feel that your reply completely missed the
purpose of what I want to do, and why. I hope the following
response clears things up.
I know that I
Roger Leigh wrote:
On Tue, Apr 07, 2009 at 09:24:38PM +0200, Adeodato Simó wrote:
+ Thorsten Glaser (Tue, 07 Apr 2009 18:54:59 +):
Except the ton which sets LC_ALL=C to get sane (parsable,
dependable, historically compatible) output.
These would then unset all other LC_* and LANG and LANGU
Andrew McMillan wrote:
On Tue, 2009-04-07 at 22:32 +0200, Adeodato Simó wrote:
It is my impression that more packages than mksh could use an UTF-8
locale at build time (I’m afraid I don’t have pointers, but I’m sure
I’ve come across at least a couple).
Wouldn’t it be just better to change Debia
Roger Leigh wrote:
> I wasn't aware that this level of checking was performed, though
it does make sense. But, does it not reject non 7-bit input in the C
locale for completeness?
Should tools doing "raw" I/O not be using lower level interfaces
such as fread() and fwrite() rather than the "for
Roger Leigh wrote:
On Mon, Apr 06, 2009 at 11:09:17AM -0700, Steve Langasek wrote:
On Mon, Apr 06, 2009 at 05:33:35PM +, Thorsten Glaser wrote:
If you need a specific locale (as seems from "mksh", not
sure if it is a bug in that program), you need to set it.
You can only set a locale on a
Thorsten Glaser wrote:
For the mksh regression tests, I need a UTF-8 locale working; most
systems either provide “en_US.UTF-8” or “en_US.utf8” with the former
being recommended.
Build-depending on locales-all has worked for me so far, except it
won’t do in Kubuntu where said package does not exi
Raphael Hertzog wrote:
After having accepted the patch, I wondered where it should be documented
and Nils pointed me to the policy section. So I asked him to submit a bug
here.
I fail to see any problem with telling people outside of Debian that they
can freely use "X-" fields for their private
Nils Rennebarth wrote:
Package: debian-policy
Version: 3.8.0.1
Severity: wishlist
Please add something along the following lines to the section 5.7
"User defined fields" to the debian policy manual:
Usually, unknown fields are iggnored by the debian packaging system. To
avoid conflicts of user
Marc Lehmann wrote:
> when having two servers with the following link lines (without passwords
etc.):
I assume you intend to use 10.0.0.x. The address space 1.x.x.x is yet
unallocated,
but not for local use.
then despite trying to connect,t he other server will instantly close the
conen
As Joerg has just said on d-d-a, some new sections have been added to
the archive. I've attached a patch for policy to bring it up-to-date.
The list become complex, considering also the priorities of sections.
Could we ask ftp-master to give us a fixed-URL to the list of sections,
the meaning a
Wouter Verhelst wrote:
On Thu, Mar 05, 2009 at 11:03:57AM +0100, Giacomo A. Catenazzi wrote:
Jon Dowland wrote:
A brief explanation as to their meaning. Doom games are
divided into engine and world-resource components. The
former is captured by 'doom-engine'.
I don't understan
Jon Dowland wrote:
A brief explanation as to their meaning. Doom games are
divided into engine and world-resource components. The
former is captured by 'doom-engine'.
I don't understand why we need a 'doom-engine' virtual package.
[i.e.: avoid circular dependencies].
IMHO, a user will select a
Gürkan Sengün wrote:
Hello Burkhard
since I'm maintaining these packages anyway, it wouldn't mind doing
that within the official distribution.
However, I'm not a DD, so I need someone to sponsor me, right?
Are you proposing to do so? And if so, what is the first step to get me
startet?
I'm s
Steve Langasek wrote:
On Sat, Feb 28, 2009 at 06:32:45PM +0100, Giacomo Catenazzi wrote:
Hmmm. I partially agree, but then we have an unnecessary exception:
such virtual packages must have only one "provider", or else there
will be problems (IIRC) on dpkg, apt or ddbuild, if such dependency
is d
Giacomo A. Catenazzi wrote:
Steve Langasek wrote:
On Thu, Feb 26, 2009 at 03:42:39PM +0100, Holger Levsen wrote:
But as this would hardcode exim4 as the default MTA for Debian in a
number
of packages, some better solutions have been proposed in
http://lists.debian.org/debian-devel/2008/05
Steve Langasek wrote:
On Thu, Feb 26, 2009 at 03:42:39PM +0100, Holger Levsen wrote:
But as this would hardcode exim4 as the default MTA for Debian in a number
of packages, some better solutions have been proposed in
http://lists.debian.org/debian-devel/2008/05/msg00381.html with the best
choi
Michael S. Gilbert wrote:
Dear All,
First of all, congratulations on getting the Lenny release out the
door! I understand that it was a lot of work, and you're probably
looking forward to at least somewhat of a break. So I don't want
to treat this problem with too much urgency (yet), but I wou
Russ Allbery wrote:
Kel Modderman writes:
It is the opinion of myself and Petter Reinholdtsen, maintainers of the
sysvinit package, that the last sentence of §9.3.1 of policy is no
longer relevant and should be removed:
"""Also, if the script name ends in .sh, the script will be sourced in
ru
Russ Allbery wrote:
"Adam D. Barratt" writes:
The Policy section detailing the "Distribution" field in .changes files
specifies that the field may contain a space-separated list of
distributions. Whilst this is technically accurate, the feature has been
deprecated since the "testing" distribut
Russ Allbery wrote:
Russ Allbery writes:
I did a bit more research based on Osamu Aoki's excellent work.
Currently, these things are referred to using three different terms:
* dak calls them components.
* The current Debian Policy document calls them categories.
* The Social Contract calls th
Russ Allbery wrote:
> Alternatively, we could document the permitted character set for the name
portion of the Maintainer field and exclude commas. It's annoying to do
this since commas have been supported in the past (in Maintainer, they're
unambiguous) and have only become a problem in Upload
Russ Allbery wrote:
Package: debian-policy
Version: 3.8.0.1
Severity: minor
I read through the shared library sections of Policy a few times last night
and can't find anywhere where Policy unambiguously recommends always
including a version in SONAME for public libraries. If you don't have a
ve
Note: I'm not a CTTE member.
Steffen Joeris wrote:
Maintainer:
--
The problem is as follows. The submitter sees the inclusion of the
getweb script as a violation of the DFSG. The script is provided by
upstream to download non-free firmware from his upstream webpage. The
package inc
Martin Mares wrote:
I think that changing the format of the file (with other suffix) would
also be helpful, i.e. instead of using tab-indent I would explicitly
writing vendor id (ev. other implicit ids) in every line.
In this manner it is easier to grep for hardware, and also to merge
files fr
Martin Mares wrote:
Dropping this information in the udeb is if course a good way of saving
space, but the full package should contain everything.
In the future (after Lenny), I would like to solve one more problem:
with the current rate of development of new hardware, the pci.ids file
is getti
Mark Brown wrote:
On Thu, Aug 28, 2008 at 01:05:19PM +0200, Johan Walles wrote:
2008/8/28 Giacomo A. Catenazzi <[EMAIL PROTECTED]>:
auth.log was invented for this reason, and separated to standard log:
it should be readable only by root, because users do errors.
It's readable
Johan Walles wrote:
Hi Nico!
Let's keep debian-security in the discussion to see what others have
to say about this.
Technically I agree with you when you say that people shouldn't enter
anything but their usernames at the login prompt, but the fact is that
people (like me and the bug submitter
Matt Arnold wrote:
> #471287 is _NOT_ an upstream issue! Furthermore if you had been paying
> attention to the bug report logs you would have noticed
I think the user wrongly interpreted "upstream".
We are "upstream" from Ubuntu, but we are not the real/initial upstream.
>> No, the patch is wrong
Russ Allbery wrote:
Raphael Hertzog <[EMAIL PROTECTED]> writes:
On Sat, 12 Jul 2008, Raphael Geissert wrote:
As demonstrated by the following trivia[1], and also mentioned by
SUSv3, the echo built-in varies from implementation to implementation
and thus should be discouraged.
Well, you jus
My G11 keyboard seems to be flaking somewhat. This results in
unpredictable USB disconnects, followed by near-immediate reconnects
on the same port.
I've also noticed it: I connected Logitech headphone to keyboard usb,
which caused power problem and thus disconnecting usb.
but I've not yet a r
Giacomo A. Catenazzi wrote:
At the end of the process, I would like to have a glossary
(maybe included into the policy)
To simplify the discussion, I created:
http://wiki.debian.org/PolicyGlossary
It contain important term and links to policy.
ciao
cate
--
To UNSUBSCRIBE, email
Russ Allbery wrote:
"Giacomo A. Catenazzi" <[EMAIL PROTECTED]> writes:
OTOH, the 'Release' file uses the dak terminology, and the name is
encoded on some tools. The most visible is apt: apt_preferences(5) for
pining use the term "Component".
Because is not
Russ Allbery wrote:
Ian Jackson <[EMAIL PROTECTED]> writes:
Russ Allbery writes:
So as a purist, I would prefer `category'. `Area' works too since it
refers to an `area' in the FTP site.
I did a bit more research based on Osamu Aoki's excellent work.
Currently, these things are referred to
William Pitcock wrote:
- epic4 (impossible to get an exception, dead contributors)
You are wrong to the "impossible to get an exception, dead
contributors", in this sentence and in other sentences:
The copyright go to the heirs, so you could contact the
heirs.
Anyway, we should follow the c
Russ Allbery wrote:
This proposal asks that Policy mandate a location to which init scripts
must log verbose errors. The original proposal was made in 2002 and there
was little subsequent discussion in 2003. This Policy proposal is also
not currently widely implemented in the archive and hence
Manoj Srivastava wrote:
Hi,
On Fri, 02 May 2008 17:45:30 +0200, Carl Fürstenberg <[EMAIL PROTECTED]>
said:
Policy section 3.8, about essential packages, doesn't explain when/why
essential is neccessary, only that it should not be essential if it's
not necessary.
My understanding is th
Russ Allbery wrote:
"Giacomo A. Catenazzi" <[EMAIL PROTECTED]> writes:
"web browser to display an URL."
I don't like the sentence, but anyway I don't worry much,
because the program should be sensible, and open browser
only with correct protocols.
I'v
Russ Allbery wrote:
--- a/policy.sgml
+++ b/policy.sgml
@@ -8675,6 +8675,68 @@ name ["syshostname"]:
for games (X and non-X games) should be installed in
/usr/share/man/man6.
+
+
+ Web browsers
+
+
+ Some programs have the ability to launch a
Here is one patch to solve the bashism in this package.
No, the patch is wrong!
BTW "-n" is not a bashism, but a long time convention starting
from the *BSD, IIRC, and cited also on POSIX.
From POSIX:
: A string to be written to standard output. If the first
: operand is -n, or if any of the o
What is the status of this bug?
I see that you changes few time the bug title,
so now is it really RFP?
Do you have a preliminary version?
If I don't see a reply in next few days, I'll
pack a new version.
ciao
cate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsu
diff -u awardeco-0.2/debian/changelog awardeco-0.2/debian/changelog
--- awardeco-0.2/debian/changelog
+++ awardeco-0.2/debian/changelog
@@ -1,3 +1,11 @@
+awardeco (0.2-2.1) unstable; urgency=low
+
+ * Non-Maintainer Upload at BSP in Zurich: fix rc bug
+ * Use the C99 bit length integer, to be sa
Jelmer Vernooij wrote:
Am Montag, den 14.01.2008, 08:43 +0100 schrieb Giacomo Catenazzi:
and the diff
PS: This bug will close also a rc-bug in an other package.
Please don't upload this. I'm not sure what upstream package you're
looking at but tdb_setalarm_sigptr() still exists in upstream g
1 - 100 of 159 matches
Mail list logo
