Software descriptions in need of editing appear to be in chromium-desktop-gnome and chromium-desktop-kde and I plan to edit them myself. My present understanding is that these packages are editable through openSuse (https://bugzilla.opensuse.org/show_bug.cgi?id=977941#c23), but a search in https://build.opensuse.org/project/new_package_branch/home:NickLevinson resulted in “Failed to branch: Package does not exist.” On the other hand, if these are Google’s (Chromium’s) packages (implied by https://www.rpmfind.net/linux/rpm2html/search.php?query=chromium-desktop-gnome&submit=Search+…&system=&arch= and https://www.rpmfind.net/linux/rpm2html/search.php?query=chromium-desktop-kde), since a Chromium developer said that a substantive fix is coming soon and there’s no point to stopping that in order to edit a statement that will soon be obsolete anyway (https://bugs.chromium.org/p/chromium/issues/detail?id=620360#c3), my editing these may eat up people’s time and delay the code fix. The rpmfind.net pages linked to only one site per package and that site is a dead-end due to redirection to a bug list. But if these packages are openSuse’s and can be edited through openSuse, how do I locate them?
On Wed 22 Jun 2016 03:46:04 AM CDT, NickLevinson wrote:
Software descriptions in need of editing appear to be in
chromium-desktop-gnome and chromium-desktop-kde and I plan to edit them
myself. My present understanding is that these packages are editable
through openSuse
(977941 – chromium update: deleting stored passwords without warning), but a search
in http://tinyurl.com/hldyomy resulted in “Failed to branch: Package
does not exist.” On the other hand, if these are Google’s (Chromium’s)
packages (implied by RPM resource chromium-desktop-gnome and
RPM resource chromium-desktop-kde), since a Chromium developer said that a
substantive fix is coming soon and there’s no point to stopping that in
order to edit a statement that will soon be obsolete anyway
(https://bugs.chromium.org/p/chromium/issues/detail?id=620360#c3), my
editing these may eat up people’s time and delay the code fix. The
rpmfind.net pages linked to only one site per package and that site is a
dead-end due to redirection to a bug list. But if these packages are
openSuse’s and can be edited through openSuse, how do I locate them?
Hi
As indicated in your bug, branch, change and submit…?
https://build.opensuse.org/package/show?project=network%3Achromium&package=chromium
osc bco network:chromium chromium
Also note there is no Novell, it no longer exists, this is openSUSE no
more, no less.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.26-21-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
“As indicated in your bug, branch, change and submit…?”: meaning? I didn’t know how to interpret your question. I can’t branch them until I can find them somewhere where I can branch them. I followed your link but the list there didn’t include these two packages. Perhaps the packages don’t operate inside Chromium but are run as part of the OS; that’s how openSuse categorizes them in update lists when I update my laptop. But maybe they’re not openSuse’s packages, although openSuse uses them and even though the software descriptions are specific to openSuse. If they’re not, then they look like they might belong to Google/Chromium. Is that your understanding, too?
Novell, Suse, and openSuse are still together. They’ve come to be owned by Micro Focus. This was anticipated in <http://www.pcworld.com/article/2684352/micro-focus-buying-novell-suse-linux-owner-for-12-billion.html>. See also <https://www.suse.com/newsroom/post/2015/suse-is-now-part-of-micro-focus>.
Hi
Create an account on OBS, https://build.opensuse.org/ this will give you a location (home:<username>, then install osc, configure osc, branch the package, fix and submit…
https://en.opensuse.org/openSUSE:OSC
Novell has been absorbed by Microfocus, openSUSE is aligned with SUSE and nothing to do with Novell.
No, I’m looking for the locations of the packages, not the location of my home page for this work, which I’ve already seen. As noted above, the site said, “Package does not exist.”
There’s a Web interface method for this and I’m using that. I tried the CLI in root (your converting the CLI-instructional URL to show a smiley was cute) but was told that PackageKit is blocking zypper and I don’t know enough to know if turning PackageKit off will be okay. I’ll stick with the Web interface.
The Investor Relations subdomain’s home page at http://investors.microfocus.com/ says, “Principal brands of Micro Focus International are: Attachmate, Borland, Micro Focus, NetIQ, Novell and SUSE.” The history at https://www.suse.com/company/history says, “SUSE joins the Micro Focus Group 2014”. The logout page for this site at https://www.suse.com/common/util/logout.php says, “Get one account for Novell, SUSE, NetIQ, PartnerNet and openSUSE”. Corporately, they may operate in separate divisions, though.
Any clues on the packages’ locations?
On Fri 24 Jun 2016 12:26:01 AM CDT, NickLevinson wrote:
No, I’m looking for the locations of the packages, not the location of
my home page for this work, which I’ve already seen. As noted above, the
site said, “Package does not exist.”
<snip>
Any clues on the packages’ locations?
Hi
It was in my previous link… this is the development project which is
where you changes need to occur…
https://build.opensuse.org/package/show?project=network%3Achromium&package=chromium
osc bco network chromium
This then creates a 'branch in you home repo, you fix and submit bacvk
to the development project.
–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.26-21-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I tried that link the first time and again last night. Its list grew by one package but still it does not list these two, so therefore I can’t branch from that list. My guess is Suse/openSuse doesn’t have either of these packages and the Google/Chromium organization’s development system probably has both.
Are you trying to do more than <just> edit a description, are you trying to make sure a warning displays so the User can then decide whether to proceed with the upgrade or not?
Assuming you really want to implement a warning and not just modify a package description,
For something so substantial as changing where passwords are stored,
I strongly suspect (without checking) that the code you want to alter or supplement is in the main Chromium project, with the Gnome gnome-keyring and KDE kwallet implementations created in those projects but still ultimately submitted to the main Chromium project.
Therefor,
If you really want to accomplish something,
I highly recommend not focusing on whoever does any packaging but instead on the Chromium code itself.
Be aware this requires <a lot> of disk space and is a <very> big build, awhile back I did this… When you build “chromium” you build not just the web browser, you’re also building chromeos, and targeting a variety of platforms. The alternative is to just submit a bug to the chromium people and let someone else who already has a dev set up to do what you request.
https://www.chromium.org/Home
https://www.chromium.org/developers/how-tos/get-the-code
TSU
The larger project is already underway by a Chromium developer (https://bugs.chromium.org/p/chromium/issues/detail?id=620360#c3). I won’t try that myself, because of the time needed to become expert in it and because two of us working on the same file/s could result in bungled toe-crunching dances or at least unfortunate delays. From the issues I raised, a warning would be needed unless passwords are kept, but apparently they are, so, therefore, no warning is needed. The software descriptions are contrary to that, but the solution to that is to edit the software descriptions. That’s a simpler project with much less risk of development conflicts.
I want to edit the software description if it’s in an openSuse package. I don’t want to edit the sofware description if it’s in a Google/Chromium package. The reason I don’t want to edit it if it’s in a Google/Chromium package is that the Google/Chromium package is due to be fixed or revised anyway and, as I understand it, the software description built into it will be edited as part of that process by a Google/Chromium developer. That’ll take a little longer but it looks like it’ll get done. But if it’s in an openSuse package then it probably won’t get edited unless I edit it. In that case, if the software description is in an openSuse package, I want to edit it.
You suggest or hint that the packages might be in Gnome’s and KDE’s development websites. I Googled “‘chromium-desktop-gnome’ inurl:gnome.org” and “‘chromium-desktop-kde’ inurl:kde.org” but didn’t find the packages in those websites.
Do you know who has either of the packages? They’re <chromium-desktop-gnome> and <chromium-desktop-kde>.
Hi
What part of this is the openSUSE development package https://build.opensuse.org/package/show?project=network%3Achromium&package=chromium don’t you understand?
Look at the spec file, here you will find the descriptions your wanting to edit… they are subpackages.
The openSUSE package is created from the upstream source chromium, it is then customized for openSUSE requirements, so if your wanting to make changes to the openSUSE package the above link is the place to do it by branching, modifying and submitting…
If you want to make a change upstream from openSUSE, then head to the developers as well with a patch. Generally upstream don’t care about distribution specific customizations/branding, package descriptions etc.
I think there is some confusion or misunderstanding what a “Package description” is, or for that matter any similar type of file which is or is similar to a manifest compared to invoking a pop up or other similar warning to the User…
An invoked <warning> is triggered by code and is not simply something found in a description somewhere.
Even if you wanted your warning to be invoked by “higher level” code which might be injected by the the openSUSE package instead of upstream, it’s still code and can’t likely be invoked only by a description file (Well, it might be technically possible if you don’t care about spaghetti code).
TSU
Thank you for telling about “spec”. I didn’t know about that one. Inside that, it looks like what I need. Next time I’m online, I should work on it.
I don’t think a pre-update warning is worth the effort right now, since patching is underway anyway. What I want to edit is the description shown to users who click a button to “Review” an update. Right now, it’s misleadingly wrong.
And, by the way, I don’t know of anyone who approves of spaghetti code (unless there’s no alternative possible) and I have no desire to introduce any.
Thanks.
I’m trying to submit what’s done but I’m apparently trying it wrong. I edited the chromium.spec file within the Build service (not on my machine) and it officially “succeeded” for two architectures (i586 and x86_64) for openSuse 13.2. I edited a copy of chromium.changes locally on my machine. Apparently, building the spec file produced four files (chromium-desktop-gnome-51.0.2704.106-882.1.i586.rpm and -kde- (instead of -gnome-) and, for both, .ix86_64. instead of .i586.). I tried Submit Package via the Web interface but that got Error 404. I installed osc and tried osc add and listed the short (as above) and full URLs for the four files but the short ones were not recognized and the long ones got the message that obs-service-download_url is needed and I guess I don’t have that. I put chromium.changes on my machine but osc vc doesn’t see it. I understand I should put everything into one package (that word “package” is written surrounded with angle brackets and not quote marks) before submitting but I don’t see an instruction on how, so I thought I’d submit chromium.changes separately, but I don’t know if that’s an acceptable procedure. I don’t see a suggestion to email the files as attachments, so maybe that’s not acceptable. How should I proceed? Thank you.
Hi
Do you have a link to the package on OBS?
Yes.
Waiting may be needed. I edited chromium.changes and maybe that’s causing the package to be “building”, even though chromium.spec was successfully built (“succeeded”) a few days ago and all I edited today looks like a text file (chromium.changes), but maybe it’s rebuilding everything anyway. The other day, it took roughly two hours on Suse’s/openSuse’s servers, so I assume that’s what it should take this time. It probably started by 9:15p EDT. Due to success the other day, I expect success this time, too.
One detail change: The chromium.changes file with my edit is now online, not just on my machine or flash drive, so that’s progress. So now chromium.spec and chromium.changes should be online in one place.
I’m not sure which link to provide, but the following list should include one link that’s useful:
-
https://build.opensuse.org/package/show/home:NickLevinson:branches:home:NickLevinson/chromium?rev=2 (with Overview tab preselected)
-
https://build.opensuse.org/package/submit_request_dialog/home:NickLevinson:branches:home:NickLevinson/chromium (this gets me an Error 404 page (“the page you are looking for does not exist”) even though I’m logged in) (I got this URL via the “Submit package” link on https://build.opensuse.org/package/show/home:NickLevinson:branches:home:NickLevinson/chromium?rev=2 (same URL as first URL above))
-
http://download.opensuse.org/repositories/home:/NickLevinson/openSUSE_13.2/ (if this is all dated 28 Jun including drill-down contents even after the latest building is done then it probably does not include chromium.changes revised tonight, Jun. 30/Jul. 1 per time zone)
Thank you very much for helping. Please let me know what I should do.
Hi
Not sure why it doesn’t have all the repos, don’t think it branched properly… But if it submits (as in creates a submit request aka SR) hopefully all is ok…
How do I make the “Submit package” link on https://build.opensuse.org/package/show/home:NickLevinson/chromium work? All it has ever given me is an Error 404 page. Following the instruction on the Error 404 page to search for the submit request dialog gets me a dead-end Error 403 page.
Instead, I’m downloading the built stuff to my laptop, but it looks like that will take 9-12 hours or so, with me standing (not sitting) in front of my laptop. Then I’ll have to upload it into OBS, and I assume that means another 9-12 hours or so, while still standing. If I have to go to the bathroom, I have to stop downloading or uploading and start again at the beginning of whatever file (there are only 3) I was in the middle of. This is not doable.
I think if I can command OBS to transfer the files within its own server intranet, especially if I can walk away and it’ll still do the transfer once I’ve started it, it’ll actually get done.
Suggestions to make the link work? Or, if not that link, some other way to make OBS move or process the files without downloading to my laptop and uploading back again?
Hi
If you have osc installed;
cd <your local obs dir>/home:NickLevinson/chromium
osc sr -m "Clarification/correction to chromium-desktop-gnome and chromium-desktop-kde"
That’s because the service file is running (428MB), but you seem to have created two branches hence the 404…?
You also need to fix the changes file, add returns at 67 characters in the changes file;
- Clarification/correction to chromium-desktop-gnome and chromium-desktop-kde software descriptions due to passwords preservation reported by Chromium developer
Change to
- Clarification/correction to chromium-desktop-gnome and
chromium-desktop-kde software descriptions due to passwords
preservation reported by Chromium developer.
I edited *.changes and now everything is building again, but it can build without me around, so that’s not so bad. The 3 files total roughly 560MB and, as far as I can see, I have only one branch. I have osc but apparently everything has to be local (I tried the URL to no avail), and requiring local storage means 9-12 hours or so to download it to be local and I imagine osc is no faster for the uploading, so that will be about 18-24 hours while I stand at this counter. Isn’t there some way I can do the process within the OBS or openSuse servers?
Hi
There is an osc option to not let the service run so it won’t download --noservice.