Please backport ndisgtk 0.7

Bug #124444 reported by Stephen Drake
6
Affects Status Importance Assigned to Milestone
Feisty Backports
Won't Fix
Undecided
Unassigned
Baltix
Invalid
Undecided
Unassigned

Bug Description

Shouldn't be too difficult as the dependencies are all in Feisty anyway and it solves some of the main bugs in the version 0.6.
I've installed through prevu and it works great for me.

Stephen Drake (spd106)
description: updated
Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Build Started: ndisgtk

This is a notification that the automatic backport of ndisgtk from gutsy to feisty has started.

You will be notified again once the build is finished.

For additional info and build logs, please see: http://sharkattack.media.mit.edu/inventory/check_builds/20

Thanks,

The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Notification of build SUCCESS for ndisgtk

Howdy! This message is to inform you that the build you requested of ndisgtk from gutsy to feisty has been completed.
Its status is: SUCCESS
For further information, build logs, and testing .deb packages, please see: http://sharkattack.media.mit.edu/inventory/check_builds/20

Thanks,
The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Build Started: ndisgtk

This is a notification that the automatic backport of ndisgtk from gutsy to feisty has started.

You will be notified again once the build is finished.

For additional info and build logs, please see: http://sharkattack.media.mit.edu/inventory/check_builds/20

Thanks,

The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Notification of build FAIL for ndisgtk

Howdy! This message is to inform you that the build you requested of ndisgtk from gutsy to feisty has been completed.
Its status is: FAIL
For further information, build logs, and testing .deb packages, please see: http://sharkattack.media.mit.edu/inventory/check_builds/20

Thanks,
The Backports Builder

Revision history for this message
John Dong (jdong) wrote :

Disregard last set of builder messages -- system suffered mirror outage. The packages built successfully and are still available.

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Build Started: ndisgtk

This is a notification that the automatic backport of ndisgtk from gutsy to feisty has started.

You will be notified again once the build is finished.

For additional info and build logs, please see: http://sharkattack.media.mit.edu/inventory/check_builds/92

Thanks,

The Backports Builder

Revision history for this message
Automated Backports Builder (john-dong+backport-builder) wrote : Notification of build SUCCESS for ndisgtk

Howdy! This message is to inform you that the build you requested of ndisgtk from gutsy to feisty has been completed.
Its status is: SUCCESS
For further information, build logs, and testing .deb packages, please see: http://sharkattack.media.mit.edu/inventory/check_builds/92

Thanks,
The Backports Builder

Revision history for this message
John Dong (jdong) wrote :

Is this a bugfix-only release or does it have some new feature that's worthwhile? Backports is not intended for fixing bugs.

Revision history for this message
Stephen Drake (spd106) wrote :

When I first requested this backport it was to fix a rather major flaw. The gui window didn't update to show installed drivers. I suppose I should have filed a bug report instead. My mistake.

Revision history for this message
Evan Broder (broder) wrote :

Closing the feisty-backports task due to Ubuntu 6.10 (Feisty Fawn) no longer being supported.

This bug is being closed by a bot. If you feel the change was made in error, please feel free to re-open the bug. However, backports requests for Ubuntu 6.10 (Feisty Fawn) are no longer being accepted.

Changed in feisty-backports:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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