On Tue, May 27, 2003 at 07:41:34PM -0700, Brian Nelson wrote:
> > "Obvious" is a key word indicating that you need to check your
> > assumptions at the door. While I will certainly concede that changelogs
> > that spell out the nature of relevant upstream changes are more useful
> > than those wh
Steve Langasek <[EMAIL PROTECTED]> writes:
> On Tue, May 27, 2003 at 12:15:37PM -0700, Brian Nelson wrote:
>
>> 1. To show others, especially NM's, what not to do. NM's mostly learn
>>by example, and I think it helps to ensure they don't follow bad
>>examples.
>
>> 2. It's something that
On Tue, May 27, 2003 at 12:15:37PM -0700, Brian Nelson wrote:
> 1. To show others, especially NM's, what not to do. NM's mostly learn
>by example, and I think it helps to ensure they don't follow bad
>examples.
> 2. It's something that should be obvious. Producing poor quality
>chan
On Tue, 27 May 2003, Zed Pobre wrote:
> > Could you elaborate on what ways yours works better than the original
> > adduser? I'm sure Roland would love to hear about functionality
> > improvements, and I'd certainly be keen for any improvements to the
> > LDAP-specific code...
>
> My version
On Tue, May 27, 2003 at 10:40:06PM +0200, Yann Dirson wrote:
> Adam wrote:
> > So doing bts work is worthless? :)
>
> Hey, someone once wrote similar scripts to count how many bugreports
> were reported by anyone !
Try:
http://bugs.debian.org/cgi-bin/pkgindex.cgi?indexon=submitter&sortby=coun
Ç×°®µÄÍø³æ£ºÈç¹ûÕâ·âÓʼþ´òÈÅÁËÄ㣬ÎÒÉî¸Ð²»°²²¢ÖÂǸ£¡
ÓÐÓÃÊÇÐÅÏ¢£¬ÎÞÓÃÊÇÀ¬»ø¡£ÇëÄã¿´ÍêÔÙɾ£¡ ^0^
ÍøÂçʱ´ú£¬¿ÉÄÜÄãʲô¶¼ÍæÁË£¬¾ÍÊÇûÓÐÍæÍøÂç׬Ǯ¡£Ôõô˵ÄØ£¬ÓÐÇ®µÄ²»Ð¼ÓÚÍæÕâÑùµÄ¶«Î÷£¬Ã»Ç®µÄÓÖÅÂÉϵ±¡£ÒÔÎÒÀ´Ëµ£¬²»Íæ
°É£¬×ܾõµÃ×÷ΪÍø³æ»¹ÉÙÁËÒ»ÖÖÔÄÀú£¨È˼ÒÎÊÎÒÍøÉϵ½µ×Äܲ»ÄÜ׬µ½Ç®£¬ÎÒÎ޴ӻشð£
Hi!
Habe gerade die Bestätigung erhalten, das mein Kontakt-Video bei
Echter-Sex.com veröffentlicht wurde.
Jetzt kannst Du Dir mein Video ansehen. Am Ende des Videos wird meine
Kontaktadresse veröffentlicht.
Schau Dir mein privates Kontaktvideo an unter:
http://www.echter-sex.com/?ref=276505
Ja,
Package: wnpp
Version: unavailable; reported 2003-05-27
Severity: wishlist
* Package name: yaz
Version : 2.0.2
Upstream Author : IndexData
* URL : http://www.indexdata.dk/yaz/
* License : BSD-ish: http://www.indexdata.dk/yaz/doc/license.php
Description : A
On Sun, May 18, 2003 at 11:39:09PM +0200, Denis Barbier wrote:
> Hi,
>
> below is a list of source packages containing gettext .po files,
> for which binary packages do not ship any file under a LC_MESSAGES
> directory.
> There might be several reasons:
> a. Programs use gettext PO files to stor
Yann Dirson dijo [Tue, May 27, 2003 at 10:38:54AM +0200]:
> That's more or less what I'd think of as well. We can start with an
> empty security patch, and have this one grow as needed. This way, apt
> will show people they have an outdated security patch - which, BTW,
> may be more of an incenti
Adam wrote:
> So doing bts work is worthless? :)
Hey, someone once wrote similar scripts to count how many bugreports
were reported by anyone !
/me rejoices recalling he was ranked 3rd by the number of open bugs :)
Well, never mind :)
--
Yann Dirson<[EMAIL PROTECTED]> |Why make M$-Bil
Christian Kurz <[EMAIL PROTECTED]> writes:
> Hi Brian
>
> On [26/05/03 23:13], Brian Nelson wrote:
>> Anselm Lingnau <[EMAIL PROTECTED]> writes:
> [...]
>> >* Closes: #159971, #124472, #147059, #70184.
>
>> Umm, no, the changelog is for listing changes (*change* log, get it?),
>> not for just
Herbert wrote:
> Yes that isn't easy to check apart from the fact that if there isn't
> an arch update after a security update to kernel-source, then that arch
> is probably vulnerable. If you've got an idea on how this can improved,
> please let us know.
A possibility would be to define a versio
Arnd wrote:
> > Let's look at your example:
> > | Patch-name: Debian base patch
> > | Patch-id: debian
> > | Architecture: all
> > | Kernel-version: 2.4.20
> > | Depends: ptrace, isdnbonding, binfmtmisc, ethernetpadding, ...
> > |
> > | Patch-name: Pre-patch 2.4.21-pre7
> > | Patch-id: patch-2.4.21
Andreas Metzler wrote:
> It would be nice if there were documented mechanisms to move a list
> /painlessly/ from alioth to lists and vice versa, i.e. keeping the
> subscriber list and redirections for the old list addresses.
Please send me a patch to the List HOWTO I once wrote. You'll need
month
Hi there,
Since I'm overloaded with work (in and out of Debian) I'm considering
orphaning a number of packages related to astronomy, they are:
- openuniverse
- starplot
- spacechart
- yale
and
- gliese
The first three are GUIs to view astronomical date whileas the last
two include astronomic da
Josip Rodin <[EMAIL PROTECTED]> writes:
> On Tue, May 27, 2003 at 08:39:50AM -0700, Brian Nelson wrote:
>> > Perhaps a separate, concise message to debian-devel-announce?
>>
>> I doubt it would help. I see changelog abuse as an act of laziness, not
>> ignorance. Common sense says that you shoul
Sven wrote:
> Why don't we use a scheme similar to what xfree86 use for its patches.
> Sure we would need to adapt it as the patches are distributed, but we
> could well do it.
As I understand it, the xfree86 package uses (some derivative of) dbs,
in which the package maintainer has to order the
Luca - De Whiskey's - De Vitis <[EMAIL PROTECTED]> wrote:
> You people told me that:
> - If i make a change to a package i've to list my changes in the package
> changelog (Matt Zimmerman, no one ever objected this).
> - If i build a new upstream, i've to list each change in the upstream
> chang
Package: wnpp
Version: unavailable; reported 2003-05-27
Severity: wishlist
* Package name: drivel
Version : 0.9.1
Upstream Author : Todd Kulesza <[EMAIL PROTECTED]>
* URL : http://sourceforge.net/projects/drivel/
* License : GPL
Description : A LiveJourna
On Tue, May 27, 2003 at 11:43:22AM -0500, John Hasler wrote:
> Brian Nelson writes:
> > If you're not going to describe upstream fixes in the changelog, then
> > don't close the bug in the changelog. The changelog is for describing
> > changes, not listing meaningless numbers.
>
> If you want to
On Tue, May 27, 2003 at 08:39:50AM -0700, Brian Nelson wrote:
> > Perhaps a separate, concise message to debian-devel-announce?
>
> I doubt it would help. I see changelog abuse as an act of laziness, not
> ignorance. Common sense says that you should be listing changes in the
> changelog. It's
Brian Nelson writes:
> If you're not going to describe upstream fixes in the changelog, then
> don't close the bug in the changelog. The changelog is for describing
> changes, not listing meaningless numbers.
If you want to have rigid, detailed rules for the content and structure of
changelog ent
On Tue, May 27, 2003 at 08:31:39AM -0700, Brian Nelson wrote:
> Uhh, your packages include the upstream source, and therefore the
> upstream source is "part of your package working".
So it is part of my work, and changes to my work should be included in
changelog.Debian...
> > To demostrate how m
On Tue, May 27, 2003 at 05:12:22PM +0200, Mathieu Roy wrote:
> I can.
> You wrote that you have "to list each change in the upstream
> changelog" to know which bug can be declared as closed. Right?
That is what i wrote, but is not what i meant: it have a difference meaning if
you take it out of t
David Nusinow <[EMAIL PROTECTED]> writes:
> Another point of note is that nascent packagers are encouraged to adopt
> other software that's already in the archive before packaging new
> items. In this case, he is merely following that advice.
Granted. OTOH, applications may be a better place to
Paul Slootman <[EMAIL PROTECTED]> writes:
> On Mon 26 May 2003, Brian Nelson wrote:
>
>> Umm, no, the changelog is for listing changes (*change* log, get it?),
>> not for just closing bugs without any reason given whatsoever.
>>
>> Why do so many seem to have difficulty with this concept? Is it
Luca - De Whiskey's - De Vitis <[EMAIL PROTECTED]> writes:
> On Tue, May 27, 2003 at 10:47:15PM +1200, Nick Phillips wrote:
>> If your changelog merely says "New upstream version, closes: #123 #456",
>> it's no help whatsoever, and I will (rightly) think that you suck.
>
> This is debian-devel: as
Luca - De Whiskey's - De Vitis <[EMAIL PROTECTED]> a tapoté :
> > You said you have "to list each change in the upstream changelog" to
> > know which bug can be declared as closed. And that's, as maintainer,
> > your job, isn't it? But is it users job to do it too?
>
> I do not understand that: c
Package: wnpp
Version: unavailable; reported 2003-05-27
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: libfilesys-statvfs-perl
Version : 0.68
Upstream Author : Ian Guthrie <[EMAIL PROTECTED]>
* URL :
* http://www.cpan.org/modules/by-mo
On Tue, May 27, 2003 at 07:14:28AM -0500, Luca - De Whiskey's - De Vitis wrote:
> The contraddiction of all this tread, is that: if i make a change to a package
> i've to list my change in the package changelog (Matt Zimmerman, no one ever
> objected this). If i build a new upstream, i've to list e
On Tue, May 27, 2003 at 03:11:11PM +0200, Michael Banck wrote:
> Didn't you just complain that people said you wouldn't have common
> sense?
>
> How odd.
Not that odd: if someone feels to be in the position of telling me that i've no
common sense or express any other kind of colorful expression a
On Tue, May 27, 2003 at 03:10:36PM +0200, Mathieu Roy wrote:
> Anybody has the right to express a point of view on anybody else work,
> right?
I'll try to keep in mind this gentlemen example of "expressing a point of view
on
anybody else work" next time, so i'll not misunderstend it with an offen
Thus spake PPMW:
> dear sirs,
>
> does VMware also support 64-bit x86 systems > HP i2000 itanium
>
> ... what do we need?
http://www.debian.org/ports/ia64/
The HP i2000 is mentioned as "working well" with Debian ia64.
--
Nathan Poznick <[EMAIL PROTECTED]>
Not that I'm ag
Luca - De Whiskey's - De Vitis <[EMAIL PROTECTED]> a tapoté :
>
> You discriminate and offend people only by reading a list of
> changes, and i should be the one who suks (supposing i'm not right)?
He has the right to think that you sucks at filling changelogs,
regarding how you fill changelogs.
On Tue, May 27, 2003 at 07:14:28AM -0500, Luca - De Whiskey's - De Vitis wrote:
> To demostrate how much this issue is stupid, i'll make any one here
> happy by including the entire upstream changelog in
> changelog.Debian.gz, next time i'll build a new upstream.
Didn't you just complain that peop
dear sirs,
does VMware also support 64-bit x86 systems > HP i2000 itanium
... what do we need?
paul!
_
NOTE: This message is for the named person's use only. It may contain
confidential, proprietary or legally privileged i
On Tue, May 27, 2003 at 10:47:15PM +1200, Nick Phillips wrote:
> If your changelog merely says "New upstream version, closes: #123 #456",
> it's no help whatsoever, and I will (rightly) think that you suck.
This is debian-devel: as soon as one declares he stops reading a thread,
beasts came out an
debian-devel:您好!
消除视频干扰,诚信圣通
网址：www.spwe.com
在CCTV系统中，当摄像机与显示终端的距离大于200米以上时，就容易出现二者接地电位有差异，
当接地电位大于一定幅值时，视频信号就会出现干扰的条纹信号，严重的甚至视频信号严重扭曲，
乃至无法观看。采用地线回路平衡器，即可消除接地环路电压带来的干扰以及空间电磁波带来的干扰。
广泛用于CCTV的各个行业，如：安防、交通、铁路、电力等。
相关热门产品：远传无噪音监听器
诚信圣通公司网站：http://www.spwe.com
联系电话：010-66027364、010-66026820
传 真：01
On Mon 26 May 2003, Brian Nelson wrote:
> Umm, no, the changelog is for listing changes (*change* log, get it?),
> not for just closing bugs without any reason given whatsoever.
>
> Why do so many seem to have difficulty with this concept? Is it
> worthwhile to Cc this stuff to -devel, or should
On Tue, May 27, 2003 at 08:16:59PM +1000, Russell Coker wrote:
> On Tue, 27 May 2003 19:04, Arnd Bergmann wrote:
> > > Here I suppose the pre-patch is supposed to be applied first, and then
> > > the application of the debian patch would only trigger application of
> > > those dependant patches not
On Tue, May 27, 2003 at 12:46:02AM -0400, Matt Zimmerman wrote:
> > * Matt Zimmerman <[EMAIL PROTECTED]> [030526 21:41]:
> > > It is _not_ obvious, and "closes: #..." gives no clue to someone reading
> > > the changelog what might have been changed. Internet access, knowledge
> > > of debbugs, et
On Tue, 27 May 2003 19:04, Arnd Bergmann wrote:
> > Here I suppose the pre-patch is supposed to be applied first, and then
> > the application of the debian patch would only trigger application of
> > those dependant patches not provided by the pre-patch.
>
> The order in which the patches are appl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 27 May 2003 17:45, Victor Torrico wrote:
> RTC does not work either compiled as a module or into the kernel. A
> patch for this is needed or a new kernel-source-2.5.69 package is needed.
In 2.5.69 many things are not working... there are m
On Tue, May 27, 2003 at 12:47:10AM -0400, Matt Zimmerman wrote:
> It is. Unfortunately, common sense is not always as common as we would
> like.
Are you trying to say that i've no common sense?
ciao,
--
Luca - De Whiskey's - De Vitis | Elegant or ugly code as well
aliases: Luca ^De
RTC does not work either compiled as a module or into the kernel. A patch for
this is needed or a new kernel-source-2.5.69 package is needed.
Cheers,
Victor
On Tue, May 27, 2003 at 12:42:29AM -0400, Matt Zimmerman wrote:
> Or better:
>
> 1. discover security vulnerability
> 2. was it fixed in the Debian package?
> 3. read changelog
> 4. see a bunch of completely worthless "Closes:" messages
> 5. throttle maintainer
1. defenestrate loser maintainers
2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 27 May 2003 10:27, Yann Dirson wrote:
> Let's look at your example:
> | Patch-name: Debian base patch
> | Patch-id: debian
> | Architecture: all
> | Kernel-version: 2.4.20
> | Depends: ptrace, isdnbonding, binfmtmisc, ethernetpadding, ...
>
Matt Zimmerman <[EMAIL PROTECTED]> wrote:
>
> All definite benefits. The one thing which seems to be missing is to ensure
> that the arch-specific kernels do not miss out on important fixes (such as
> security) to the main kernel source tree.
Yes that isn't easy to check apart from the fact that
On Tue, May 27, 2003 at 07:37:42AM +0200, Sven Luther wrote:
> On Tue, May 27, 2003 at 07:23:27AM +1000, Herbert Xu wrote:
> > On Mon, May 26, 2003 at 10:00:06PM +0200, Yann Dirson wrote:
> > >
> > > We could get around Guido's point mentionned above by having a list of
> > > default patches to ap
Arnd wrote:
> Actually, I was thinking of a different concept with a 'Replaces: tag,
Hm. As I understand it, it would be more something like a "Provides:"
declaration, it seems. Such a feature does not seem useless to me at
first glance (we already see aglomerations of patches, like FOLK,
which
reopen 159971
reopen 124472
reopen 147059
reopen 70184
thanks
Anselm Lingnau <[EMAIL PROTECTED]> writes:
> Format: 1.7
> Date: Tue, 27 May 2003 01:15:33 +0200
> Source: bwidget
> Binary: bwidget
> Architecture: source all
> Version: 1.6.0-1
> Distribution: unstable
> Urgency: low
> Maintainer: An
On Monday 26 May 2003 22:30, Kai Henningsen wrote:
> [EMAIL PROTECTED] (Gerfried Fuchs) wrote on 26.05.03 in
<[EMAIL PROTECTED]>:
> As for the long descriptions, I really don't see what the use is in an
> ITP. The packages will of course have them.
A proper long description will help avoid ques
On Tue, May 27, 2003 at 07:23:27AM +1000, Herbert Xu wrote:
> On Mon, May 26, 2003 at 10:00:06PM +0200, Yann Dirson wrote:
> >
> > We could get around Guido's point mentionned above by having a list of
> > default patches to apply, which would by default contain the debian
> > patch.
>
> Yes, but
* Joachim Breitner <[EMAIL PROTECTED]> [2003-05-26 18:05:11 +0200]:
> Am Mon, 2003-05-26 um 17.15 schrieb Philipp Matthias Hahn:
> > Or do you expect everbody to file duplicate bugs or subscribe to
> > existing bugs ?
>
> AFAIK you can't subscribe to single bugs (at least I was told that a few
> m
55 matches
Mail list logo
