Launchpad itself

Incorrect auto-blacklisting in DSD?

Bug #841372 reported by Stefano Rivera
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I notice libsdl-sound1.2 is blacklisted (BLACKLISTED_CURRENT) in oneiric
https://launchpad.net/ubuntu/oneiric/+localpackagediffs?field.name_filter=libsdl-sound1.2&field.package_type=all

If this was done automatically, it was incorrect.

Is this a symptom of LP: #785657?

Tags: derivation
Revision history for this message
Julian Edwards (julian-edwards) wrote :

It's a good idea to note the versions that were blacklisted in case it changes again. FTR, they are:
1.0.3-3.1 in Sid and 1.0.3-3build1 in Oneiric.

Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Stefano Rivera (stefanor) wrote :

I'm hoping it *will* change again, because I want to do the sync :P Should I go ahead?

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 841372] Re: Incorrect auto-blacklisting in DSD?

On Sunday 04 September 2011 23:16:49 you wrote:
> I'm hoping it *will* change again, because I want to do the sync :P
> Should I go ahead?

Yup :)

Revision history for this message
Stefano Rivera (stefanor) wrote :

Also worth noting, when versions are the same in Debian and Ubuntu, they aren't auto-blacklisted

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On Monday 05 September 2011 13:55:20 you wrote:
> Also worth noting, when versions are the same in Debian and Ubuntu, they
> aren't auto-blacklisted

That's intentional - they are marked "resolved".

Revision history for this message
Iain Lane (laney) wrote :

On Mon, Sep 05, 2011 at 02:15:24PM -0000, Julian Edwards wrote:
> On Monday 05 September 2011 13:55:20 you wrote:
> > Also worth noting, when versions are the same in Debian and Ubuntu, they
> > aren't auto-blacklisted
>
> That's intentional - they are marked "resolved".

Still, the sync checkbox should be greyed out if the differences are
resolved.

Revision history for this message
Stefano Rivera (stefanor) wrote :

> That's intentional - they are marked "resolved".

But the sync checkbox isn't greyed out in the UI.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

On Monday 05 September 2011 15:51:05 you wrote:
> > That's intentional - they are marked "resolved".
>
> But the sync checkbox isn't greyed out in the UI.

Argh. I filed bug 841934 to track this.

Revision history for this message
Stefano Rivera (stefanor) wrote :

Spotted another one:
p7-rar: sid: 9.20.1~ds.1-3 oneiric: 9.04~ds.1-1

Revision history for this message
Stefano Rivera (stefanor) wrote :

p7zip-rar I mean

Revision history for this message
Steve Langasek (vorlon) wrote :

I just ran into this problem with freetype for precise. wheezy is at 2.4.6-2, precise is at 2.4.7-1; the blacklist causes 'syncpackage' to demand a --force to import the newer version. Stefano thinks it's this same bug. I'm not sure why any blacklist entry would need to be generated when wheezy is *behind* precise, but maybe I don't understand how the blacklisting works?

Revision history for this message
Julian Edwards (julian-edwards) wrote :

The blacklisting code is a bit of a mess - if anyone wants to tackle this then look at _updateVersionsAndStatus() inside lib/lp/registry/model/distroseriesdifference.py

(see also bug 785657 which talks about fixing the mess)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.