[opensuse-kde] KDE:Current is "broken"?
Hi all, Just when we[1] finally got around to updating Tumbleweed to the latest KDE packages, it looks like the whole repo is broken with tons of "conflicts". Any idea what happened? Any guess as to when it will be fixed? thanks, greg k-h [1] Well, Jiri, not me, he did all the real work here, I just ran the script he updated :) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dear Greg, On Thursday 19 June 2014 09:40:22 Greg KH wrote:
Just when we[1] finally got around to updating Tumbleweed to the latest KDE packages, it looks like the whole repo is broken with tons of "conflicts".
Please, send next time just an email to the people that are maintaining that particular repository, before this is being picked up by users in the wrong way. KDE:Current is in a good state and does NOT have any conflicts. I don't know where you got that idea from, but I guess you misinterpret something.
Any idea what happened? Any guess as to when it will be fixed?
During the update to 4.13.2, the packages were copied from KDE:Distro:Factory and still contained the link to openSUSE:Factory. This morning coolo accepted the 4.13.2 update also in Factory and due to this the link caused an issue with the existing packages and therefore the OBS packages got into a broken state. Simply removing the link to the package in Factory resolved the issue. So please next time contact the KDE team directly instead of using this mailinglist for issues regarding moving a KDE update to TW Regards Raymond On Thu, Jun 19, 2014 at 6:40 PM, Greg KH <gregkh@linux.com> wrote:
Hi all,
Just when we[1] finally got around to updating Tumbleweed to the latest KDE packages, it looks like the whole repo is broken with tons of "conflicts".
Any idea what happened? Any guess as to when it will be fixed?
thanks,
greg k-h
[1] Well, Jiri, not me, he did all the real work here, I just ran the script he updated :) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri, Jun 20, 2014 at 12:28:46AM +0200, Raymond Wooninck wrote:
Dear Greg,
On Thursday 19 June 2014 09:40:22 Greg KH wrote:
Just when we[1] finally got around to updating Tumbleweed to the latest KDE packages, it looks like the whole repo is broken with tons of "conflicts".
Please, send next time just an email to the people that are maintaining that particular repository, before this is being picked up by users in the wrong way. KDE:Current is in a good state and does NOT have any conflicts. I don't know where you got that idea from, but I guess you misinterpret something.
https://build.opensuse.org/project/monitor/KDE:Current was showing everything as "broken", so I could be forgiven for thinking that way :)
Any idea what happened? Any guess as to when it will be fixed?
During the update to 4.13.2, the packages were copied from KDE:Distro:Factory and still contained the link to openSUSE:Factory. This morning coolo accepted the 4.13.2 update also in Factory and due to this the link caused an issue with the existing packages and therefore the OBS packages got into a broken state. Simply removing the link to the package in Factory resolved the issue.
So please next time contact the KDE team directly instead of using this mailinglist for issues regarding moving a KDE update to TW
Isn't this list the way to contact the KDE team "directly"? What other way should I have done this? Now that things look like they are working, I'll continue on with the KDE tumbleweed update, thanks. greg k-h -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thu, Jun 19, 2014 at 09:40:22AM -0700, Greg KH wrote:
Hi all,
Just when we[1] finally got around to updating Tumbleweed to the latest KDE packages, it looks like the whole repo is broken with tons of "conflicts".
Any idea what happened? Any guess as to when it will be fixed?
Ok, as people got mad the last time I said this, yet provided no other way to find out how to fix this, I'd like to report a number of "broken" packages in the KDE:Current repo right now, with the same type of "conflicts" as happened before. What causes this to happen? What workflow is broken that generates it? Examples of this "brokenness" is KDE:Current/libprison and KDE:Current/python-kde4. Some other packages seem to have been removed, like KDE:Extra/plasmoid-quickaccess, any reason for this? Any way to get notified when package removal / addition happens so that I can be sure to keep Tumbleweed up to date? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sunday 06 of July 2014 19:34:39 Greg KH wrote:
On Thu, Jun 19, 2014 at 09:40:22AM -0700, Greg KH wrote:
Hi all,
Just when we[1] finally got around to updating Tumbleweed to the latest KDE packages, it looks like the whole repo is broken with tons of "conflicts".
Any idea what happened? Any guess as to when it will be fixed?
Ok, as people got mad the last time I said this, yet provided no other way to find out how to fix this, I'd like to report a number of "broken" packages in the KDE:Current repo right now, with the same type of "conflicts" as happened before. Thanks, this has now been resolved.
What causes this to happen? What workflow is broken that generates it? This happened as packages where linked to Factory, and meanwhile changed there.
Examples of this "brokenness" is KDE:Current/libprison and KDE:Current/python-kde4.
Some other packages seem to have been removed, like KDE:Extra/plasmoid-quickaccess, any reason for this? It has been removed from Factory (sr229321), thus also from KDE:Extra.
Any way to get notified when package removal / addition happens so that I can be sure to keep Tumbleweed up to date? Good question. I guess we could set up a wiki page where we could mark new/removed packages... Other suggestions welcome =)
Cheers, Hrvoje
thanks,
greg k-h
On Mon, Jul 07, 2014 at 01:04:29AM +0200, šumski wrote:
On Sunday 06 of July 2014 19:34:39 Greg KH wrote:
On Thu, Jun 19, 2014 at 09:40:22AM -0700, Greg KH wrote:
Hi all,
Just when we[1] finally got around to updating Tumbleweed to the latest KDE packages, it looks like the whole repo is broken with tons of "conflicts".
Any idea what happened? Any guess as to when it will be fixed?
Ok, as people got mad the last time I said this, yet provided no other way to find out how to fix this, I'd like to report a number of "broken" packages in the KDE:Current repo right now, with the same type of "conflicts" as happened before. Thanks, this has now been resolved.
What causes this to happen? What workflow is broken that generates it? This happened as packages where linked to Factory, and meanwhile changed there.
Examples of this "brokenness" is KDE:Current/libprison and KDE:Current/python-kde4.
Some other packages seem to have been removed, like KDE:Extra/plasmoid-quickaccess, any reason for this? It has been removed from Factory (sr229321), thus also from KDE:Extra.
Should I also remove it from Tumbleweed? Any other package I should remove?
Any way to get notified when package removal / addition happens so that I can be sure to keep Tumbleweed up to date? Good question. I guess we could set up a wiki page where we could mark new/removed packages...
Ick, I hate wikis. Anything I can "subscribe" to to see the changes happen? Otherwise I can just live with occasional breakage like this, email works for it. greg k-h -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (4)
-
Greg KH -
Greg KH -
Raymond Wooninck -
šumski