Wouter Verhelst wrote:
> On Sat, Jul 30, 2005 at 08:30:51PM -0400, Anthony DeRobertis wrote:
> They shouldn't be, as they're not supposed to be complete sentences
> either (think of it as "package -- short description", as in "foo -- a
> program to do something", or even "foo -- do something")
Ye
> On Sun, 2005-07-31 at 23:10 +0400, Nikita V. Youshchenko wrote:
> > (3) allow new upstream into stable.
>
> But, how would be the proposed process for this software?
>
> I mean, should they also have some kind of grace period after uploading
> to unstable? Would it enter stable after unstable? O
Jose Carlos Garcia Sogo wrote:
>
> You can also add the epoch number to your own packages. Thus, they will
> be always newer than those coming from Debian, so they won't be
> upgraded. Of course you don't have to add epochs to upstream sources.
> That is not the goal of an epoch.
>
Upstream prov
On Mon, Jul 25, 2005 at 07:45:39PM -0600, Marcelo E. Magallon wrote:
> After some fiddling with AptPkg, my first cut at generating a list
> of packages ready to be transitioned is attached.
After getting fed up with AptPkg I rewrote the script in the attached
form. If you feed the script t
Helge Kreutzmann wrote:
> leo is a program for the command line which translates German words
leo is a command-line program that translates...
> into their English counterpart and vice versa using dict.leo.org.
Suggestion: "Equivalent" instead of "counterpart."
> This packages needs libnet-d
OK, I've summarized all (I think) of Policy's requirements on packages
in the wiki page, together with a cite to the section it came from.
Also, I've completed "news", and would appreciate any feedback.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Conta
2005-07-31 (日) の 22:34 +0200 に Ondrej Sury さんは書きました:
> On Sun, 2005-07-31 at 15:32 +0200, Andreas Barth wrote:
> > Hi,
> >
> > libdb4.1 should be removed from Debian soon. The following packages
> > still use it (but could move forward to the more recent db4.2 or db4.3
> > package):
> >
> > libed
On Sun, 2005-07-31 at 23:10 +0400, Nikita V. Youshchenko wrote:
> (3) allow new upstream into stable.
But, how would be the proposed process for this software?
I mean, should they also have some kind of grace period after uploading
to unstable? Would it enter stable after unstable? Or after testi
Tshepang Lekhonkhobe <[EMAIL PROTECTED]> writes:
>> I ended up downgrading to xfree86 from testing, and then upgraded back up
>> to xorg from unstable (and all that went smoothly).
>
> I was also using ubuntu's xorg on Sid, but unlike you I am still
> unable to install xserver-xorg and xserver-comm
In article <[EMAIL PROTECTED]> you wrote:
> We can't keep the same ABI and toolchain forever, can we?
Well, currently Solaris is doing bit advertisemet that they did not (never?)
break compatibility. However since I am not into C++ ABI I cant comment if
the current interface is ok or not. It is ju
On Sun, Jul 31, 2005 at 08:22:26AM -0600, Wesley J. Landaker wrote:
> On Sunday 31 July 2005 00:19, Andreas Barth wrote:
> > we currently have almost 800 RC bugs in etch due to small glitches that
> > started to make code FTBFS with the new gcc version.
> > It is urgently necessary that maintainer
[ Forwarded to -devel for discussion ]
On Tue, Jun 28, 2005 at 02:30:16PM +0100, Steve McIntyre wrote:
>On Mon, Jun 27, 2005 at 01:54:32PM +0200, Simon K?gstr?m wrote:
>>Package: seyon
>>Version: 2.20c-16
>>Severity: grave
>>Justification: renders package unusable
>>
>>seyon does not work when gno
Package: wnpp
Severity: wishlist
Owner: Stefano Zacchiroli <[EMAIL PROTECTED]>
* Package name: lablgtksourceview
Version : 0.0.1
Upstream Author : Stefano Zacchiroli <[EMAIL PROTECTED]>
* URL : http://helm.cs.unibo.it/software/lablgtksourceview/
* License : LGPL
W. Borgert <[EMAIL PROTECTED]> wrote:
>> (1) keep vulnerable packages in stable,
>> (2) remove affected packages from distribution,
>> (3) allow new upstream into stable.
> I'ld "vote" for (2), maybe with the goal of creating pressure
> towards upstream to take security more serious.
But how do
El dom, 31-07-2005 a las 22:20 +0200, Harald Dunkel escribió:
> Philipp Kern wrote:
> >
> > The maintainer could use an epoch to fix it. (It's like a 1: prefix.)
> >
> >
> >>2.5.130.CVS.2005.07.19.01-1
> >>2.5.13-0.CVS.2005.07.19.01-1
> >
> >
> > Is it really important to have the 0 sp
Hi,
* W. Borgert <[EMAIL PROTECTED]> [2005-07-31 23:24]:
> On Sun, Jul 31, 2005 at 11:10:04PM +0400, Nikita V. Youshchenko wrote:
> > (1) keep vulnerable packages in stable,
> > (2) remove affected packages from distribution,
> > (3) allow new upstream into stable.
> ...
> > What do you think on th
On Sun, Jul 31, 2005 at 11:10:04PM +0400, Nikita V. Youshchenko wrote:
> (1) keep vulnerable packages in stable,
> (2) remove affected packages from distribution,
> (3) allow new upstream into stable.
...
> What do you think on this?
I'ld "vote" for (2), maybe with the goal of creating pressure
to
On Sun, 2005-07-31 at 15:32 +0200, Andreas Barth wrote:
> Hi,
>
> libdb4.1 should be removed from Debian soon. The following packages
> still use it (but could move forward to the more recent db4.2 or db4.3
> package):
>
> libedataserver1.2-4
> evolution-exchange
> evolution-data-server1.2
> evol
Philipp Kern wrote:
>
> The maintainer could use an epoch to fix it. (It's like a 1: prefix.)
>
>
>> 2.5.130.CVS.2005.07.19.01-1
>> 2.5.13-0.CVS.2005.07.19.01-1
>
>
> Is it really important to have the 0 split away? I think while dashes
> are perfectly valid when there is a Debian re
Hi!
Nikita V. Youshchenko [2005-07-31 23:10 +0400]:
> So options seem to be:
>
> (1) keep vulnerable packages in stable,
> (2) remove affected packages from distribution,
> (3) allow new upstream into stable.
We recently had the same problem in Ubuntu. Adam Conrad and me both
spend literally wee
"Nikita V. Youshchenko" <[EMAIL PROTECTED]> writes:
> Maybe in rare cases like this one, when these seems to be no other way to
> keep important package set secure, we should allow new upstream into
> Debain Stable?
In this rare cases I agree otherwise the users will continue to use
vulnerable
On Sun, 2005-07-31 at 21:21 +0200, Harald Dunkel wrote:
> And how is this going to be fixed? The broken version
> number might be much higher than upstream's version
> number. AFAIK there is no way to turn it back, is it?
The maintainer could use an epoch to fix it. (It's like a 1: prefix.)
>
Jose Carlos Garcia Sogo wrote:
> El dom, 31-07-2005 a las 19:13 +0200, Harald Dunkel escribió:
>
>>Hi folks,
>>
>>What happens if a package maintainer ignores upstream's
>>version number (either on purpose, or by accident, e.g.
>>a typo)? Is this allowed?
>
>
> If it is done on purpose and for
Hello.
As it is being currently discussed on debian-security [1], security team
has hard times supporting mozilla family of packages, because of
unfriendly upstream policy - they don't want to isolate security fixes
from a large changesets of new upstream releases. And given the huge size
of t
On Sun, Jul 31, 2005 at 07:13:43PM +0200, Harald Dunkel wrote:
> What happens if a package maintainer ignores upstream's
> version number (either on purpose, or by accident, e.g.
> a typo)? Is this allowed?
It depends on the situation - for example, nis ignores the upstream
version number complet
On Sunday 31 July 2005 08:22, Wesley J. Landaker wrote:
> I don't want to rant, but since you are urging NMUs and apparently doing
> them yourself. Your recent NMU of cheeesetracker compiled it against two
> C++ ABIs; you could avoided this if you read the bug report and my
> response. Also, always
Hello,
We now have 5 versions of automake in the archive. These are necessary
because new versions of automake tend to break backwards
compatibility. We don't however need to keep all these versions around
forever. So I'd like to get automake1.6 removed from the archive. The
packages below have st
On 7/31/05, Bernd Eckenfels <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> > I don't want to rant, but since you are urging NMUs and apparently doing
> > them yourself. Your recent NMU of cheeesetracker compiled it against two
> > C++ ABIs; you could avoided this if you re
In article <[EMAIL PROTECTED]> you wrote:
> I don't want to rant, but since you are urging NMUs and apparently doing
> them yourself. Your recent NMU of cheeesetracker compiled it against two
> C++ ABIs; you could avoided this if you read the bug report and my
> response. Also, always contact th
El dom, 31-07-2005 a las 19:13 +0200, Harald Dunkel escribió:
> Hi folks,
>
> What happens if a package maintainer ignores upstream's
> version number (either on purpose, or by accident, e.g.
> a typo)? Is this allowed?
If it is done on purpose and for a given reason, it can be perfectly
valid.
retitle 319583 ITP: pcmciautils -- PCMCIA userspace utilities (Linux 2.6.13+)
thanks
I'm the maintainer of pcmcia-cs so I'm intending to package
pcmciautils.
* Package name: pcmciautils
Version : 007
Upstream Author : Dominik Brodowski <[EMAIL PROTECTED]>
* URL : http:
Hi folks,
What happens if a package maintainer ignores upstream's
version number (either on purpose, or by accident, e.g.
a typo)? Is this allowed?
Regards
Harri
signature.asc
Description: OpenPGP digital signature
Package: wnpp
Severity: wishlist
Owner: Stefan Ott <[EMAIL PROTECTED]>
* Package name: xfce4-sensors-plugin
Version : 0.6.1
Upstream Author : Fabian Nowak <[EMAIL PROTECTED]>
* URL : http://xfce-goodies.berlios.de/
* License : GPL
Description : graphical
Ok, thanks for your comments. I've uploaded a new package to lltag
webpage with the following description:
Description: Automatic command-line mp3/ogg file tagger
lltag is a command-line tool to set ID3 tags of mp3 files and Ogg tags.
It may be used to tag multiples files at once by comparing th
On Sunday 31 July 2005 00:19, Andreas Barth wrote:
> we currently have almost 800 RC bugs in etch due to small glitches that
> started to make code FTBFS with the new gcc version.
>
> It is urgently necessary that maintainers start to fix their own
> packages, and that whoever has some time at thei
Hi,
libdb4.1 should be removed from Debian soon. The following packages
still use it (but could move forward to the more recent db4.2 or db4.3
package):
arla
kerberos4kth-servers
vacation
libedataserver1.2-4
libroken16-kerberos4kth
kerberos4kth-kdc
libapache-mod-witch
libotp0-kerberos4kth
evolutio
Package: wnpp
Version: N/A; reported 2005-07-31
Severity: wishlist
* Package name: leo
Version : 2.0.0
Upstream Author : Carsten Luckmann <[EMAIL PROTECTED]>
* URL : http://www.itp.uni-hannover.de/~luckmann
* License : GPL
Description : English-German dict
On Sun, Jul 31, 2005 at 12:55:51PM +0200, Loïc Minier wrote:
> I tried following the thread on libtool and -dev inter-dependencies,
> and I'd like someone to confirm the way to go (a summary of the SUMMARY
> thread would be nice :).
> What I'm currently doing right now is adding -dev dependenc
On Sun, Jul 31, 2005 at 09:59:04AM +, W. Borgert wrote:
> - How do I have to arrange the repository, so that
better use arrangement which svn-buildpackage creates
branches trunk tags upstream build-area and tarballs
> under pkg-greetings/hello/tags/1.0-1/? Or do I have to put
> the upstrea
Hi,
I tried following the thread on libtool and -dev inter-dependencies,
and I'd like someone to confirm the way to go (a summary of the SUMMARY
thread would be nice :).
What I'm currently doing right now is adding -dev dependencies on -dev
packages for each "-l" in dependency_libs.
Hi,
what is the right/best way to build packages from SVN using
pbuilder? I am new to both, please be patient.
Suppose, I have a package with complete upstream sources (no
tarballs) under svn://svn.debian.org/svn/pkg-greetings/hello/
with the subdirectories branches/, tags/, and trunk/.
- How d
Hello,
> You must update unreviewed description daily. Checked reviewed
> descriptions again and show changes to the reviewer, if the review ist
> not finished.
Ok, did that.
Thanks for your suggestions,
--
Clément Stenac
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "uns
On Sun, Jul 31, 2005 at 10:19:30AM +0200, Laszlo Boszormenyi wrote:
> I have thousands of emails in separate maildirs. I would like to
> remove header lines from all of them that matches a pattern. AFAICR
> I have already used something similar a long time ago, but now I
> can not dig up anything.
On Sat, Jul 30, 2005 at 08:30:51PM -0400, Anthony DeRobertis wrote:
> One more question: Was the question, should short descriptions be
> capitalized? ever decided?
They shouldn't be, as they're not supposed to be complete sentences
either (think of it as "package -- short description", as in "foo
Hi,
I have thousands of emails in separate maildirs. I would like to
remove header lines from all of them that matches a pattern. AFAICR
I have already used something similar a long time ago, but now I
can not dig up anything. Is there any tool that can do this (C/C++
preferred, but Python/Perl i
Hello,
> One more question: Was the question, should short descriptions be
> capitalized? ever decided?
The policy does not answer this specific question.
Anyway, for such highly-repetitive and computer-detectable "errors",
it's not a good idea to mark the description as wrong here, it would
mak
46 matches
Mail list logo
