*** Bug 97749 has been marked as a duplicate of this bug. ***
Currently if we add an icon to a theme - we should really add a copy to the Galaxy theme as well (this should be the base of all our theme stacks).
Unfortunately this is not always done - and we end up with missing icons in the galaxy theme.
Icons themes are packed by:
if you re-run 'make postprocess' you can re-build the themes which are zip files that we stack up.
The perl script to build those is in:
When building the default (galaxy) theme we should fail hard - with a nice warning 'die ("foo");' in the perl - if we are missing any icon =)
Changing to assigned
A polite ping, still working on this bug ?
Yes, I am. I am a little stuck. So this is coded in perl, and the graphics are already in the other themes, but not this one? I have been slowing working on it and will hopefully be done within two or three weeks. I will try and work on it right now.
Am installing the dependencies and cloning the repository, will try to work on this and hopefully be done soon, if I'm not done in the next two weeks it can be opened back up, but I hope to get it done. I wish that spelling error hadn't been fixed, would have been much easier!
Am looking at the Perl scripts and graphics and will work more tomorrow, will let you know if I need help.
Have been looking at the scripts at browsing through opengrok. Am stuck. In line 24 of postprocess/CustomTarget_images.mk in opengrok there is a reference to /icon-themes/industrial. Clearly that is an outdated icon theme as stated. But I also searched through /icon-themes/galaxy and there were a lot of images in opengrok. But based on the title of the bug, what I need to do is write an automated unit test to check for graphics correct? In perl? That should throw an error/exception 'die' if there are missing graphics in the galaxy theme compared to the other themes? I'm a complete beginner, so "re-run 'make postprocess'
would be something I do in the Linux command line? Or in a Perl script? I think this is a unit test, correct? I'm fairly confused. So I'm going to ask a coworker for help on this tomorrow. Will try to connect to the irc over the weekend. I'm determined, but confused. An example of a similar issue, or unit test would be very helpful, or a step by step. But, this appears to be a unit test, that needs to be written in perl, that checks for missing graphics in the default theme compared to the other themes, correct? So is the perl script in 'solenv/bin/packimages.pl' to rebuild the themes which are stacked zip files? Or is the Perl script in solenv/bin/packimages.pl a unit test? I was confused by the 'rebuild themes' vs 'unit test'. In order to solve this bug would I need to use git and gerrit and commit to master? Or attach a perl script to test graphics here in bugzilla?
Thanks for looking at this one =)
> But based on the title of the bug, what I need to do is write an automated
> unit test to check for graphics correct ?
> In perl? That should throw an error/exception 'die' if there are missing
> graphics in the galaxy theme compared to the other themes ?
Sure - so what I'd do is hack solenv/bin/packimages.pl - to ensure that for any image we put into a theme .zip file - we check that the same image is present in the galaxy/ theme - and just die if not with some error / warning =)
> I'm determined, but confused.
No problem =)
> An example of a similar issue, or unit test would be very helpful, or a step by step. But, this appears to be a unit test, that needs to be written in perl,
So - if we can avoid creating a unit test and/or a new makefile, and just make the generic theme packing fail if this criteria is not met with a 'die' that would be wonderful and meet the need.
> So is the perl script in 'solenv/bin/packimages.pl' to rebuild the themes
> which are stacked zip files?
Seems reasonable; read it, play with it and see =) add some printouts there; do:
$ cd postprocess; make
to see what they print. After a few minutes of playing, you'll be the new expert on packimages.pl =) people tend not to remember much about every piece of code they just re-learn it when needed.
Having added this test, and test its failure (just remove a file in galaxy I guess to test), then do:
git diff -u > test.patch
and send test.patch to the mailing list =)
Alright thanks. Have been busy the past two weeks but am cracking now! thanks!
Thanks! I've been busy the past two weeks but just got cracking now!
Created attachment 127060 [details]
Rough proposed patch
After being confused, and determined, I have carefully studied packimages.pl and have come up with a rough patch. Will push to mailing list and test my code more this week. This is just using gedit, but i'm excited to finally be making headway.
Hi Diana, it looks plausible. The easiest way to send a patch is to do:
git diff > /tmp/foo.patch
and attach that - then we see the change in context etc. =)
Thanks for getting back to me quickly, unfortunately I have had my personal life get in the way, and my job, get in the way, these past couple weeks. If I am not able to finish this by Oct. 1st I will reopen it. Do I use logerrit for the patcch? Will work on Git starting Sunday.
(In reply to Diana Sedlak from comment #14)
> Thanks for getting back to me quickly, unfortunately I have had my personal
> life get in the way, and my job, get in the way, these past couple weeks. If
> I am not able to finish this by Oct. 1st I will reopen it. Do I use logerrit
> for the patcch? Will work on Git starting Sunday.
A polite ping still working on this patch ?
Do you need help, then please do not hesitate to contact me (or simply comment on the ticket)
Unassigning, seems not to be worked on. If work is still ongoing, then please assign it again.
No please remove me as the assignee.
Well that is normally something you should do yourself, and not wait for others to do it.