hello, How are you doing?
I was re-reading your page (did not for a while) and i like to suggest an
"FtL - Fail to Launch" support, again, please read me here as someone of 51
years of age who had to endure loads of unsupported experience with basics
of this "not a syndrome" issue aka the transiti
Re: Vincent Fourmond 2010-01-27
<20100127202504.8551.4855.report...@tanyaivinco.homelinux.org>
> It would be nice if the popcon entry was also displayed for ITPs
> too. Often, there is a significant number of users that did install
> unofficial packages, and knowing they are there is a motivatio
It looks like DEHS has been offline [1] for quite a few years. Since this issue
will never be fixed, I suggest that this bug report becomes closed.
[1] https://wiki.debian.org/DEHS
I hope this list is an appropriate place to reach people who handle
rebuild tests. If not can you suggest a place that is.
Some code has "timebombs", that is code that works correctly on systems
with the system clock up to a certain date but then will fail with
values of the system clock beyon
Hi,
I am also interested in such feature for `packages overview' web page. As I can
see all necessary statistics is available in database [1][2][3].
Best regards,
Boris
[1] http://popcon.debian.org/unknown/by_vote
[2] http://popcon.debian.org/unknown/by_recent
[3] http://popcon.debian.org/unkno
>> Why not? Giving a link to the PTS in the default RFA/O mail looks
>> reasonable.
>
> Ehm, I don't think so. Otherwise other "reasonable" links can be:
>
> - the bts page for the package
> - the homepage of the upstream project (if present)
> - anything else
>
I think the PTS link will be enough,
>> > I was thinking report a whislist bug against reportbug,
>>
>> No, thanks.
>
> Why not? Giving a link to the PTS in the default RFA/O mail looks
> reasonable.
Ehm, I don't think so. Otherwise other "reasonable" links can be:
- the bts page for the package
- the homepage of the upstream projec
On Mon, 05 Jul 2010, Sandro Tosi wrote:
> 2010/7/4 Elías Alejandro :
> > Hi all,
> > Maybe this isn't the place to make this suggestion but
> > I'd like know if this is posible.
> > Sometimes when I'm looking for how to collaborate with
> > Debian,
On Sun, Jul 04, 2010 at 11:10:36AM -0500, Elías Alejandro wrote:
> Hi Hauke,
> First all, thanks for your answer.
No problem.
> >> Basically it could be insert two items in the bug report body.
> >> I was thinking report a whislist bug against reportbug, but I'd like to
> >> know
> >> if this is
2010/7/4 Elías Alejandro :
> Hi all,
> Maybe this isn't the place to make this suggestion but
> I'd like know if this is posible.
> Sometimes when I'm looking for how to collaborate with
> Debian, I arrive to [1] but always find this problem for me.
> Bugs tagged
Hi Hauke,
First all, thanks for your answer.
>> Basically it could be insert two items in the bug report body.
>> I was thinking report a whislist bug against reportbug, but I'd like to know
>> if this is the correct way or maybe I'm wrong. Sorry I'm newbie about
>> this subjects.
>
> But I don't
Hi Elías,
thanks for your interest!
On Sat, Jul 03, 2010 at 05:24:34PM -0500, Elías Alejandro wrote:
> Maybe this isn't the place to make this suggestion but
> I'd like know if this is posible.
> Sometimes when I'm looking for how to collaborate with
> Debian, I ar
Hi all,
Maybe this isn't the place to make this suggestion but
I'd like know if this is posible.
Sometimes when I'm looking for how to collaborate with
Debian, I arrive to [1] but always find this problem for me.
Bugs tagged with "RFA" or "O" ,at my opinion, sho
Package: qa.debian.org
Severity: wishlist
Hello,
It would be nice if the popcon entry was also displayed for ITPs
too. Often, there is a significant number of users that did install
unofficial packages, and knowing they are there is a motivation to
move forward...
The example that comes to
reassign 279824 ftp.debian.org
retitle 279824 RM: perlftlib -- RoQA; buggy, orphaned
thanks
On Fri, Jul 25, 2008 at 08:22:50PM +0200, Moritz Muehlenhoff wrote:
> Frank Lichtenheld wrote:
> > On Wed, Jul 23, 2008 at 10:28:33PM +0200, Moritz Muehlenhoff wrote:
> > > perlftlib can be removed, I've sp
Frank Lichtenheld wrote:
> On Wed, Jul 23, 2008 at 10:28:33PM +0200, Moritz Muehlenhoff wrote:
> > perlftlib can be removed, I've sponsored the last package build-depending
> > on it recently and it's coupled to freetype 1, which won't be included
> > in Lenny.
>
> defoma still recommends it. Has
On Wed, Jul 23, 2008 at 10:28:33PM +0200, Moritz Muehlenhoff wrote:
> perlftlib can be removed, I've sponsored the last package build-depending
> on it recently and it's coupled to freetype 1, which won't be included
> in Lenny.
defoma still recommends it. Has someone verified that this can be
dro
perlftlib can be removed, I've sponsored the last package build-depending
on it recently and it's coupled to freetype 1, which won't be included
in Lenny.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 7/16/07, Steve Langasek <[EMAIL PROTECTED]> wrote:
This is a gtk+1.2 application that has seen no upstream activity since 2004;
it has 22 active users according to popcon, and there doesn't appear to be
anything I would describe as a gtk+2.0 alarm clock in the archive, but it's
one of only tw
Hi,
On Sun Jul 15, 2007 at 15:33:27 -0700, Steve Langasek wrote:
> Should sanduhr be removed from unstable?
seconded, even so it has 175 users according popcon.
--
[EMAIL PROTECTED] /root]# man real-life
No manual entry for real-life
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subj
Hi folks,
The sanduhr package has been orphaned for over a year; in the orphaning
upload, the maintainer, who is also upstream, commented that he has no time
for working on the package or the upstream software.
This is a gtk+1.2 application that has seen no upstream activity since 2004;
it has 22
Maybe the Debian package status script [1] can be moved onto a
debian.org machine.
Cause if something happens to that http://bjorn.haxx.se the script
will be unavailable.
Also good to have copy of the script local in case his machine gets
trashed for some reason and no backups.
[1] http://bjorn.
* Martin Zobel-Helas ([EMAIL PROTECTED]) wrote:
> i am not sure if i overlooked your answer to my last mail. Is there anything
> we
> can help on #232810? As we are going to freeze realy soon now (looks like both
> ends of the toolchain are fixed by now), i fear that openmosix will be
> dropped
Hello,
I've been researching RC bugs for my NM T&S part and came across the
python-pcgi package (bug #225539). After downloading the latest upstream
version of this package I found out that:
1. Upstream has a new author and he changed the program name to python-pcgi2
to avoid a name clash with an
Martin Zobel-Helas wrote:
> Stephen Frost wrote:
> > * Martin Zobel-Helas ([EMAIL PROTECTED]) wrote:
> > > question about a removal from testing:
> > >
> > > openmosix
> > >
> > > It has longstanding RC bug (#232810). No direct reaction from maintainer.
> >
> > Actually, I was working on that al
Stephen Frost wrote:
> * Martin Zobel-Helas ([EMAIL PROTECTED]) wrote:
> > question about a removal from testing:
> >
> > openmosix
> >
> > It has longstanding RC bug (#232810). No direct reaction from maintainer.
>
> Actually, I was working on that already (well, that issue was fixed, I
> was t
* Pierre Machard <[EMAIL PROTECTED]> [2004-07-18 11:55]:
[libflux0]
> QA : it seems that the maintainer is MIA. Maybe we should orphaned
> this package.
He said this package can be removed from unstable. I'll do so later.
--
Martin Michlmayr
[EMAIL PROTECTED]
* Pierre Machard <[EMAIL PROTECTED]> [2004-07-18 11:55]:
> QA : it seems that the maintainer is MIA. Maybe we should orphaned
> this package.
I've contacted him, thanks.
--
Martin Michlmayr
[EMAIL PROTECTED]
Hi,
I suggest that we remove libflux0 from testing.
No maintainer upload since 2001, RC bug related to old libtool,
and it seems that a new software is available on fluxlib.org.
This software seems deprecated.
QA : it seems that the maintainer is MIA. Maybe we should orphaned this
package.
Ch
Hullo,
On http://ftp-master.debian.org/testing/testing_probs.html would it be
possible to link the names of source packages
e.g.
* Binaries from cannot be installed:
to the relevant debcheck page on the qa website
http://qa.debian.org/debcheck.php?dist=testing&package=
This should help tracki
* Adrian Bunk <[EMAIL PROTECTED]> [011213 11:03]:
> On Tue, 11 Dec 2001, Bas Zoetekouw wrote:
> > * Colin Watson <[EMAIL PROTECTED]> [011203 15:33]:
> > > On balance I think I like the idea, provided that there are multiple
> > > people responsible for each area and that anybody's still free to wor
On Tue, 11 Dec 2001, Bas Zoetekouw wrote:
>...
> I'm sure not whether Adrian's proposal would work out or not. The idea
> of subdividing the QA tasks, I like, though. Maybe we should have a
> coordinator for each task, while at the same time allowing everyone to
> work on any task, as long as the
* Bas Zoetekouw <[EMAIL PROTECTED]> [011211 08:25]:
> I kind of agree with you here. A bit more coordination would probably be
> good, but otoh we won't want to place too much limits on what individual
> people can or should do.
I doubt much control is either proposed or necessary, but having a sm
Hi Colin!
You wrote:
> I've thought about this for a while, and I can't decide whether I think
> it's a great idea or a terrible one. :) I wouldn't like to feel
> restricted in the areas of QA work I could work on: I've done almost all
> of the things you mention at various times, depending on my
On Thu, Nov 22, 2001 at 12:42:53PM +0100, Adrian Bunk wrote:
> I'd like to hear your opinion on the following proposal:
>
> Currently QA works the way that people find something to do themselves and
> everyone works for himself at the tasks he sees. I propose to change this
> to define tasks of QA
uilder or
> to send bug reports
"Leads" for each port would be appropriate. Minimal requirements would be
simple enough to fulfill, and it would give the people stepping into those
positions an incentive to help out a little more if they are recognized.
> - WNPP
> * maintain
through all logs of
failed builds to check whether they are problems in the autobuilder or
to send bug reports
- WNPP
* maintain the WNPP bugs and the orphaned packages
I'd like to hear your opinion on:
1. the proposal
2. my suggestion of the tasks (e.g. did I miss tasks?)
cu
For the long term, it might be nice to divide tasks by difficulty. E.g.,
there could be a section for bugs that are fixed by a provided patch or
simple dependency rules, and another section for difficult debugging
work. (The intent of this being to make it easier for a beginner to sit
down and knoc
Date: Tue, 9 Feb 1999 22:35:34 +0100
From: "J.H.M. Dassen (Ray)" <[EMAIL PROTECTED]>
To: Debian bugtracking system <[EMAIL PROTECTED]>
Subject: electric-fence: Forward shared lib suggestion.
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset
Package: electric-fence
Version: 2.0.5-4
AFAIK the upstream release of Electric Fence doesn't utilise the trick of
making it into a shared library like the current Debian package does.
Please forward this trick upstream; it is very useful not to have to relink
a binary in order to use Electric Fen
Package: debian-policy
Version: 2.4.1.2
Severity: normal
I suggest that the default news server be looked for (also) in the env
var NNTPSERVER. Emacs packages and mozilla look for it, maybe others
too.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Co
41 matches
Mail list logo
