Your message dated Sun, 06 Jul 2014 15:59:33 +0000
with message-id <[email protected]>
and subject line Bug#749173: Removed package(s) from unstable
has caused the Debian Bug report #749173,
regarding RM: nvidia-settings -- ROM; moving from contrib to main
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 [email protected]
immediately.)
--
749173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749173
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ftp.debian.org
Severity: normal
Hi,
I'd like to move src:nvidia-settings from contrib to main as follows:
nvidia-settings source/contrib => source/main
nvidia-settings any/contrib => any/contrib
libxnvctrl0 any/contrib => any/main
libxnvctrl-dev any/contrib => any/main
Rationale is as follows: libxnvctrl is useful in main since it can be
used to query for availability of the NV-CONTROl X extension (that is
provided by the non-free driver) without requiring the non-free driver
to be available. At least two packages are interested in doing this:
* conky (currently has forked off a source package in contrib) and
* chromium (has an embedded copy of libxnvctrl).
The nvidia-settings binary package would stay in contrib since it
requires the non-free driver to be usable.
There are no non-free or contrib Build-Depends.
A library with similar purpose is libvdpau that also moved to main.
See #747837 for the original request against nvidia-settings.
I'm not sure what needs to be removed or otherwise prepared for doing
this switch. I'd prefer a solution that does not involve removal of
nvidia-settings from *testing*.
After this was handled in sid, we need to do the similar move in
experimental.
My last upload to sid/main of a new upstream version got rejected:
> Subject: nvidia-settings_331.79-1_amd64.changes REJECTED
>
> An exception was raised while processing the package:
> Traceback (most recent call last):
> File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 98, in
> wrapper
> function(upload, srcqueue, comments, transaction)
> File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 150, in
> comment_accept
> transaction.copy_source(upload.source, suite,
> source_component_func(upload.source), allow_tainted=allow_tainted)
> File "/srv/ftp-master.debian.org/dak/dak/process_policy.py", line 142, in
> source_component_func
> .join(Component).one()
> File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 2193,
> in one
> "Multiple rows were found for one()")
> MultipleResultsFound: Multiple rows were found for one()
>
> Original comments:
>
>
Would it be helpful if I upload this again to DELAYED/30 and ftp-master
moves it to DELAYED/0 once they have done the neccessary preparation?
Andreas
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
libxnvctrl-dev | 331.79-1 | amd64, armhf
libxnvctrl0 | 331.79-1 | amd64, armhf
nvidia-settings | 331.79-1 | source, amd64, armhf
------------------- Reason -------------------
ROM; moving from contrib to main
----------------------------------------------
Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it). Please also remember 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.
Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.
Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System. Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected].
The full log for this bug can be viewed at https://bugs.debian.org/749173
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
