Bug 172548 – Abolish overwrite alert

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 172548 - Abolish overwrite alert


Summary:	Abolish overwrite alert


Status:	RESOLVED OBSOLETE

Product:	sound-juicer
Classification:	Applications
Component:	interface
Version:	2.14.x
Hardware:	Other Linux

Importance:	Normal enhancement
Target Milestone:	---
Assigned To:	Sound Juicer Maintainers
QA Contact:	Sound Juicer Maintainers

URL:
Whiteboard:

Depends on:	172539 172543 172547
Blocks:

Reported:	2005-04-03 20:49 UTC by Matthew Paul Thomas (mpt)
Modified:	2021-05-17 15:47 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Matthew Paul Thomas (mpt) 2005-04-03 20:49:58 UTC

Distribution/Version: Ubuntu Hoary preview

Once Sound Juicer no longer overwrites files that are for different albums or
were not created by itself, there is no need for the overwrite confirmation
alert any more.

Removing the alert would make bug 130782 and bug 161315 obsolete.

Comment 1 Matthew Paul Thomas (mpt) 2005-04-03 21:01:31 UTC

If Sound Juicer can look ahead and see that the files for all remaining tracks
have already been created during a previous ripping session, this can be noted
at the bottom of the progress window, so that people know they can now safely
click "Stop" (bug 172544) if they want to. Something like "(i) All remaining
tracks were copied in a previous session." -- though that's clumsy and needs work.

Comment 2 Ross Burton 2008-02-26 14:38:16 UTC

I'm not convinced that this is feasible, especially considering I've closed 172547 as silly.

Comment 3 GNOME Infrastructure Team 2021-05-17 15:47:50 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/sound-juicer/-/issues/29.