| View previous topic :: View next topic |
| Author |
Message |
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3884
|
 Posted: Tue Oct 01, 2024 7:50 pm Post subject: media-sound/spotify stable upgrade fails [fixed] |
 |
|
| Code: | >>> Emerging (1 of 1) media-sound/spotify-1.2.47::gentoo
* spotify-client_1.2.47.364.gf06e5cee_amd64.deb BLAKE2B SHA512 size ;-) ... [ ok ]
>>> Unpacking source...
>>> Unpacking spotify-client_1.2.47.364.gf06e5cee_amd64.deb to /var/tmp/portage/media-sound/spotify-1.2.47/work
>>> Source unpacked in /var/tmp/portage/media-sound/spotify-1.2.47/work
>>> Preparing source in /var/tmp/portage/media-sound/spotify-1.2.47/work ...
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/media-sound/spotify-1.2.47/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/media-sound/spotify-1.2.47/work ...
>>> Source compiled.
>>> Test phase [not enabled]: media-sound/spotify-1.2.47
>>> Install media-sound/spotify-1.2.47 into /var/tmp/portage/media-sound/spotify-1.2.47/image
gzip: usr/share/doc/spotify-client/changelog.gz: No such file or directory
* ERROR: media-sound/spotify-1.2.47::gentoo failed (install phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 136: Called src_install
* environment, line 1888: Called die
* The specific snippet of code:
* gunzip usr/share/doc/spotify-client/changelog.gz || die;
*
* If you need support, post the output of `emerge --info '=media-sound/spotify-1.2.47::gentoo'`,
* the complete build log and the output of `emerge -pqv '=media-sound/spotify-1.2.47::gentoo'`.
* The complete build log is located at '/var/log/portage/media-sound:spotify-1.2.47:20241001-194327.log.gz'.
* For convenience, a symlink to the build log is located at '/var/tmp/portage/media-sound/spotify-1.2.47/temp/build.log.gz'.
* The ebuild environment file is located at '/var/tmp/portage/media-sound/spotify-1.2.47/temp/environment'.
* Working directory: '/var/tmp/portage/media-sound/spotify-1.2.47/work'
* S: '/var/tmp/portage/media-sound/spotify-1.2.47/work/' |
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. "
Last edited by CaptainBlood on Wed Oct 02, 2024 4:27 am; edited 1 time in total |
|
| Back to top |
|
 |
asturm
Developer
Joined: 05 Apr 2007
Posts: 9288
|
|
| Back to top |
|
|
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3884
|
| Posted: Tue Oct 01, 2024 10:03 pm Post subject: |
|
|
Yeah, a heaven place where to report about stabilization that should not have occurred, among others things.
Let's assume the mistakenly upgrade sequence: | Code: | emerge -C media-sound/spotify
eclean-dist --deep |
It would currently lead to the loss of the media-sound/spotify app until current ebuild is fixed; Because former installed
media-sound/spotify package would be:
1) locally deleted.
2) likely removed from the internet.
| Code: | cat /etc/eclean/distfiles.exclude
# /etc/eclean/distfiles.exclude
# In this file you can list some categories or cat/pkg-name for which you want
# to protect distfiles from "ecleaning". You can also name some specific files.
# See `man eclean` for syntax details.
.layout.conf*
.mirror-cache.json
layout.conf
metadata.dtd
metadata.xsd
portage-\d\d\d\d\d\d\d\d\.tar\.bz2
spotify-client* |
| Code: | cat /etc/eclean/packages.exclude
# /etc/eclean/packages.exclude
# In this file you can list some categories or cat/pkg-name for which you want
# to protect binary packages from "ecleaning".
# See `man eclean` for syntax details.
media-sound/spotify |
final line of both these files are here to prevent such a consistency failure.
Side note 1: Users may feel hassled when requested to provide emerge --info and ebuild.log when reporting (such a request is actually justified, most of the time) .
However I'm not sure providing ebuild log is conditional to ebuild publishing. 
Side note 2: As far as emerge --info and ebuild.log claims are concerned those 2 files could be merged into ones, emerge --info included in ebuild log. This is only up to portage team...
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22698
|
| Posted: Tue Oct 01, 2024 11:14 pm Post subject: |
|
|
| CaptainBlood wrote: | Let's assume the mistakenly upgrade sequence: | Code: | emerge -C media-sound/spotify
eclean-dist --deep |
|
If we assume users make mistakes, shall we not assume a far more serious mistake, such as unmerging glibc? Users are advised to avoid emerge -C because it is so dangerous and can so easily do serious damage. | CaptainBlood wrote: | It would currently lead to the loss of the media-sound/spotify app until current ebuild is fixed; Because former installed
media-sound/spotify package would be:
1) locally deleted.
2) likely removed from the internet. |
That is a risk with any package, which is why cautious users do not use emerge -C, do not purge their distfiles immediately after an unmerge, and do keep xpak binpkgs for reinstallation. | CaptainBlood wrote: | | Side note 1: Users may feel hassled when requested to provide emerge --info and ebuild.log when reporting (such a request is actually justified, most of the time) . |
What is your point here? If it is justified, then users should be expected to provide it, and should be asked to provide it when it is missing and necessary. | CaptainBlood wrote: | | However I'm not sure providing ebuild log is conditional to ebuild publishing. |
What is the question here? The bug report that asturm cited has all the standard details, and those details were provided without a reminder, even though some of it probably is not necessary in this specific case. | CaptainBlood wrote: | | Side note 2: As far as emerge --info and ebuild.log claims are concerned those 2 files could be merged into ones, emerge --info included in ebuild log. This is only up to portage team... |
They are easier to handle when separate. | CaptainBlood wrote: | | Has this ebuild even been tested internally prior to publishing? |
I agree that it seems like this was a serious miss, but your question adds no value to the bug and serves only to antagonize the developer, who likely already knows this was a mistake. It looks like this bump was due to media-sound/spotify-1.2.42 - [meson] [libtool] [gcc-15] !!! Couldnt download spotify-client_1.2.42.290.g242057a2_amd64.deb. Aborting. The Spotify upstream removed their older deb, which broke installing the previous stable. |
|
| Back to top |
|
|
CaptainBlood
Advocate
Joined: 24 Jan 2010
Posts: 3884
|
| Posted: Wed Oct 02, 2024 4:22 am Post subject: |
|
|
GURU: sys-libs/glibc deletion is a mistake, publishing or stabilizing untested is an ERROR and not preventing it to happen is an organizational BLUNDER. 
FUBU: And it seams it ain't gonna change any soon (cf report penultimate comment status).
Providing an build log internally when publishing an new or upgrading ebuild to the portage tree could help though.
Let's stay cool 'til the next one... 
How long would it have taken to validate?: | Code: | qlop -tv media-sound/spotify
2024-10-02T00:22:17 <<< media-sound/spotify-1.2.47: 4s |
Much less time than what it took to the reporter to generate and join all his attachments.
As far as build process is concerned, if 2 files are preferable, why not generate an emerge --info / emerge -p -v files along with the build.log?
It would bring an easier workflow to reporting, should it be for beginners or in postponed mode...
I still think a single file with emerge -pv + emerge --info + build log (in that order) is quite manageable with home/end keyboard keys.
Better reporting & more reporting from users can only be beneficial to the community as a whole with no cost for the gentoo dev team imho.
Thks 4 ur attention, interest & support.
_________________
USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
| Back to top |
|
|
asturm
Developer
Joined: 05 Apr 2007
Posts: 9288
|
| Posted: Wed Oct 02, 2024 11:48 am Post subject: |
|
|
| CaptainBlood wrote: | | And it seams it ain't gonna change any soon (cf report penultimate comment status).:wink: |
Seems like you were proven wrong there, again. (and again) (and again ...) |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
