[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#757162: marked as done (whitedune: please package newer upstream version)

Your message dated Tue, 09 Dec 2025 12:11:22 +0000
with message-id <[🔎] E1vSwYs-003RCr-0a@fasolo.debian.org>
and subject line Bug#1114505: Removed package(s) from unstable
has caused the Debian Bug report #757162,
regarding whitedune: please package newer upstream version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
757162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757162
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: whitedune
Version: 0.30.10-1.1
Severity: normal
Control: submitter -1 Joerg Scheurich <mufti@zentux.rus.uni-stuttgart.de>

On 2014-08-05 22:35:57, Joerg Scheurich wrote:
> Hi,
> 
> Unfortuneatly, i dont know how how to start a new debian bugmessage from 
> a system with "reportbug" but without working email.
> Mail is handled with a external system, which is handled via ssh.
> Therefore i send the errormessage in this mailinglist.

Just send the message that reportbugs generates in the mail program of
your choice to submit@bugs.debian.org. I've added the address to CC to
create the bugreport and I've set you as submitter.

Cheers

Original bug report:
> Package: whitedune
> Version: 0.30.10-1.1
> Severity: normal
> 
> Version 0.30.10-1.1 of package whitedune is not able to read/write X3D 3.3
> (from november 2013) commmands. The new stable update 0.99pl64 support
> this commands, but do not render them.
> Additionly version 0.99pl64 have hundreds of additional feature/bugfixes
> compared to version 0.30.10-1.1
> 
> |   * What led up to the situation?
> 
> A long time between stable versions of upstream whitedune
> 
> |   * What exactly did you do (or not do) that was effective (or
> |     ineffective)?
> 
> I am the upstream and wrote a new stable version with respect to
> X3D 3.3
> 
> The following files may be usefull for a debian update:
> 
> http://129.69.35.12/dune/whitedune_0.99pl64-1.diff.gz
> http://129.69.35.12/dune/whitedune_0.99pl64-1.dsc
> http://129.69.35.12/dune/whitedune_0.99pl64-1_i386.changes
> http://129.69.35.12/dune/whitedune_0.99pl64-1_i386.deb
> http://129.69.35.12/dune/whitedune_0.99pl64.orig.tar.gz
> 
> -- System Information:
> Debian Release: 7.6
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: i386 (i686)
> 
> Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
> ...
> 
> so long
> MUFTI
> -- 
> << "<" <
> 
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Version: 0.30.10-2.2+rm

Dear submitter,

as the package whitedune has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1114505

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)

--- End Message ---
Reply to: