Your message dated Tue, 29 Sep 2015 13:03:35 +0200
with message-id <[email protected]>
and subject line Re: cheese: Cheese 3.18 breaks Gnome Contacts 3.18
has caused the Debian Bug report #800427,
regarding cheese: Cheese 3.18 breaks Gnome Contacts 3.18
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.)
--
800427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800427
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cheese
Version: 3.16.1-1
Severity: normal
Dear Maintainer,
Can we seriously cross-reference the test harness dependencies to figure out
that when other packages upgrade to GNOME 3.18.0 [Example: gnome-contacts] that
adjacent packages, like Cheese 3.18.0 don't break and uninstall already the
latest 3.18 packages?
Seriously, this entire upgrade along with the GCC 5 transition is an
abomination.
Finish the GCC 5 transition with GNOME 3.16 and then move in 3.18. Too many
breaks make zero sense. The Fact gnome-control-center is built but the rquired
libgdesktop 3.12 is non-existent and those packages are uploaded to
Experimental anyways speaks volumes to the problems not being mitigated to
avoid the end user from taking a bath on broken packages.
- Marc
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cheese depends on:
ii cheese-common 3.16.1-1
ii gnome-video-effects 0.4.1-3
ii libc6 2.21-0experimental1
ii libcanberra-gtk3-0 0.30-2.1
ii libcheese-gtk23 3.16.1-1
ii libcheese7 3.16.1-1
ii libclutter-1.0-0 1.24.0-1
ii libclutter-gtk-1.0-0 1.6.4-1
ii libgdk-pixbuf2.0-0 2.32.0-1
ii libglib2.0-0 2.46.0-2
ii libgnome-desktop-3-10 3.16.2-2
ii libgstreamer1.0-0 1.6.0-1
ii libgtk-3-0 3.18.0-2
Versions of packages cheese recommends:
ii gnome-icon-theme 3.12.0-1
ii gvfs 1.25.92-1
ii hicolor-icon-theme 0.13-1
ii nautilus-sendto 3.8.2-1
ii yelp 3.16.1-1
Versions of packages cheese suggests:
pn gnome-video-effects-frei0r <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Hello Marc J. Driftmeyer.
On Tue, Sep 29, 2015 at 12:49:46AM -0700, Marc J. Driftmeyer wrote:
> Package: cheese
> Version: 3.16.1-1
> Severity: normal
>
> Dear Maintainer,
>
> Can we seriously cross-reference the test harness dependencies to
> figure out that when other packages upgrade to GNOME 3.18.0 [Example:
> gnome-contacts] that adjacent packages, like Cheese 3.18.0 don't break
> and uninstall already the latest 3.18 packages?
I'm not a native english speaker which might add to making it hard
for me to understand what you're talking about here, but I think
the main problem is not on my end...
- you file a bug against cheese 3.16.1-1
- you talk about cheese 3.18.0 (!!!)
- you talk about "cross-reference the test harness" (????)
- you talk about dependencies without stating which particular ones.
>
> Seriously, this entire upgrade along with the GCC 5 transition is an
> abomination.
- Then you go on rambling about GCC....
>
> Finish the GCC 5 transition with GNOME 3.16 and then move in 3.18. Too
The cheese transition has not been started. You are (yet again)
installing things for *Experimental* here. You're supposed to be very
involved with exactly what is going on in development before even
looking at Experimental.
Secondly why do you think that cheese (written in C) has anything to do
with a transition about the C++ standard library?!
>From a cheese point of view, just get rid of C++ from the system if it's
causing you problems.
> many breaks make zero sense. The Fact gnome-control-center is built
> but the rquired libgdesktop 3.12 is non-existent and those packages
> are uploaded to Experimental anyways speaks volumes to the problems
> not being mitigated to avoid the end user from taking a bath on broken
> packages.
The transition will be handled once it's started (in Unstable).
Right now a transition slot has not even been requested from the release
team (eg. there's no bug report on
http://bugs.debian.org/release.debian.org about cheese 3.18).
As you can see from http://packages.qa.debian.org/cheese there is a need
for a transition, listed as "auto-cheese".
In Debian when reporting bugs please try to stick to answering the
questions in the reportbug template. As a general recommendation always
include atleast the answer to these three questions when reporting an
issue: What did you do? What happened? What did you expect to happen?
Handwaving and Random ramblings doesn't help at all in trying to
communicate an understanding of what issue you're experiencing and
identifying the problem.
I'm closing this bug report considering that "if your system breaks when
installing from Experimental you get to keep both halves" is the
documented and expected way to work with *Experimental* (aka.
rc-buggy).
Please either start involving and informing yourself more about debian
development or stop using Experimental.
Transitions are not handled until things hits Unstable and then it's
(supposed to be) solved/finished when it goes into Testing. If you want
to change how Debian works (not only for gnome but in general) you
want to start doing the work yourself.... That's how you do changes
in Debian. You do the work, then you get to decide how... If you don't
want to do the work, then (assuming you don't want to look like a fool)
stop telling others how they should do their work.
Regards,
Andreas Henriksson
PS. Bug reports are very welcome, but please try to achive some level
of relevance and usefulness when opening bug reports by talking about
a particular issue and describe how it can be reproduced and what
consequenses it has.
--- End Message ---
