Re: bug 284925

2005-11-06 Thread Florian Weimer 
* Thomas Bushnell:

> What is expected of me with respect to bug 284925?  I would like to
> close it; a DSA was given for the version in stable, it refers to
> woody only, etc, something like that.  I don't understand the details,
> but I'd like to close it.  What should I do?

You should acknowledge the NMU of 1.9.14-17.1 and make sure that these
changes are applied.  Ah, you did that, but since the bug was filed
against two packages, it didn't have the intended effect.

The changelog mentions only CAN-2004-1026.  Maybe you could check that
CAN-2004-1025 is fixed as well, and mention it in the changelog?
I'll see if I can find a copy of Red Hat's SRPM.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

bug 284925

2005-11-06 Thread Thomas Bushnell BSG 

What is expected of me with respect to bug 284925?  I would like to
close it; a DSA was given for the version in stable, it refers to
woody only, etc, something like that.  I don't understand the details,
but I'd like to close it.  What should I do?

Thomas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: suggest binNMUs for all arches: python2.[2,3]-libplot

2005-11-06 Thread Steve Langasek 
On Sun, Nov 06, 2005 at 05:23:07PM -0500, Nathanael Nerode wrote:
> (regarding python2.1-libplot and python2.2-libplot)
> >Both are apparently packages for obsolete versions of python, with no
> >reverse dependencies.  Why don't we push for their removal instead?

> Quite right.  I hadn't checked reverse dependencies this time.  What's
> the best way to do this; ask the maintainer to withdraw them?

Yes, as done now in 337441 and 337094.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature

Re: How to get KDE in: total analysis

2005-11-06 Thread Nathanael Nerode 

>You obviously know where the upstream bug systems are;
>wouldn't it be more helpful to take the initiative and forward thesebug
>reports yourself?

Actually, it probably wouldn't.

The first request upstream will make is to test on an stock version of
GCC, rather than Debian GCC.  The upstream bug systems require a real 
submitter.  If I submit the bugs, I end up as the 'reporter' for the 
bug, and will be asked to do this.  I will also be asked to test fixes, etc.


Well, I can't. I don't even have access to the necessary hardware, 
unlike (for example) every Debian developer -- and so it's not 
appropriate for me to be in that situation.  If someone who actually can
respond to the needs of upstream reports the bug, it would be much, much 
better.





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: suggest binNMUs for all arches: python2.[2,3]-libplot

2005-11-06 Thread Nathanael Nerode 

(regarding python2.1-libplot and python2.2-libplot)
>Both are apparently packages for obsolete versions of python, with no
>reverse dependencies.  Why don't we push for their removal instead?

Quite right.  I hadn't checked reverse dependencies this time.  What's
the best way to do this; ask the maintainer to withdraw them?




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: xerces upgrade/transition

2005-11-06 Thread Jay Berkenbilt 
Steve Langasek <[EMAIL PROTECTED]> wrote:

> Actually, depending on the details, uploading xerces27 during the KDE
> transition might have made things *easier*... oh well. :)

/me experiences brain gears turning

How's that?  Because some packages could have switched from depending
upon libraries that were tangled in the transition to libraries that
weren't?  Or more fundamentally, because transition xerces27 into
testing doesn't make anything uninstallable since xerces25 and
xerces26 are still there and then moving applications that depend upon
xerces25 of xerces26 over to xerces27 results in the transition of
xerces25 and xerces26 no longer making those applications
uninstallable?  Perhaps having uploaded xerces27 and getting gdal and
friends to switch to it would have broken the link between icu/xerces
and unixodbc, thereby allowing them to transition on their own.  gdal
wouldn't have been able to go, but it wouldn't have been keeping
xerces out.  Is that right, or am I still missing something?

I didn't think this through far enough in my planning.  I was just
thinking that wedging xerces27 between icu and gdal would get it
tangled up with the transition as well, forgetting that icu is, at
present, not both a direct and indirect dependency of anything and
also forgetting the effect of xerces27 not being in testing.

I am now filing away that this type of situation may have consequences
that aren't immediately obvious to me since I have no direct
experience with dealing with the actual impact of these actions.  It's
remarkable how much experience guides intuition.

--Jay


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: testing security status (post kde)

2005-11-06 Thread Florian Weimer 
* Steve Langasek:

> Heh.  Would it be worth posting summaries of the unfixed RC security bugs
> somewhere from time to time, to try to get more people involved with NMUing
> them?  Or are most of these not RC security bugs at this point?

There is  (based
on the testing team data), which should mostly up to date.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: xerces upgrade/transition

2005-11-06 Thread Steve Langasek 
On Sat, Nov 05, 2005 at 11:06:59AM -0500, Jay Berkenbilt wrote:

> I'm going to upload xerces27-2.7.0 soon.  This is supposed to be the
> last version in the xerces 2.x series.  It has been out for some time,
> but I didn't want to upload it until the KDE transition was finished.
> (Congratulations on that!)  This should be a near-zero-impact
> transition, but I'm alerting the release team as requested.  Details
> follow.

[snip]

That looks fine to go ahead with, thanks for letting us know.

Actually, depending on the details, uploading xerces27 during the KDE
transition might have made things *easier*... oh well. :)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


signature.asc
Description: Digital signature