[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [GSoC] blends-gen-control hints (Was: blends-dev, gsoc 2013)



Hello Andreas,



On Fri, Sep 13, 2013 at 01:04:33AM +0300, Emmanouil Kiagias wrote:
> I was idle the past 2-3 days due to some exams I had to take for my
> university.

I hope you were successfully passing te exams. ;-)

I also hope so, thanks :-)

I think we just need some more testing with real life cases:

I tried again debian-edu:

.../debian-edu $ make dist
...
if [ ! -f dependency_data/debian-edu_1.713~svn81933.json ]; then \
                echo "dependency_data/debian-edu_1.713~svn81933.json does not exist, can not generate changelog dependencies-changes entry"; \
                exit -1; \
        fi
if [ ! -f dependency_data/debian-edu_1.712.json ]; then \
                echo "dependency_data/debian-edu_1.712.json does not exist, can not generate changelog dependencies-changes entry"; \
                exit -1; \
        fi
dependency_data/debian-edu_1.712.json does not exist, can not generate changelog dependencies-changes entry
/bin/sh: 3: exit: Illegal number: -1
make[2]: *** [changelogentry] Fehler 2


Modulo I did something wrong (which could be fixed by the documentation
you intend to write) some polishing is needed.  There is also some room
for better error handling.
 
Every dependency json file for each Blend should exist into dependency_data folder. Like the files you get when you run the ./dumpTags script (like you did for debian-med to generate the json files from svn tags). The changelogentry needs the json dependency files for the two latest releases so it can compare them and add the differences into the latest  release's changelog as an automatic entry. The json dependency file for the latest release is automatically generated/updated from the statusdump rule everytime the make dist is called. So in your case it tries to compare the debian-edu_1.713~svn81933 release with the debian-edu_1.712.json. As I wrote before the latest debian-edu_1.713~svn81933.json  is automatically generated parsing the current tasks/ folder from the debian-edu but it can not find the json file for the debian-edu_1.712.json (the dependency json file for the previous release), that's why it dumps:

dependency_data/debian-edu_1.712.json does not exist, can not generate changelog dependencies-changes entry
(you can can check the dependency_data folder to see that the json file for the latest release is properly generated but it also needs for the previous one)

But you are right all these should be well documented.

Apropos documentation:  We just have the Blends documentation inside the
blends-dev package.  What I told you previously is that I *really* see
your work as continuation of the current blends-dev package - so we
should keep the changelog and all the other stuff like the
documentation.
 
Yes I keep this in mind. The reason I have not merged the previous changelog entries as we said into blends-gsoc for the moment is that blends-gsoc contains the control file for blends-dev and not for all the blends source generally so I keep it like that for the moment so I can properly generate the package for testing. We can merge the changelog entries once we merge the blends-gsoc into blends source.

 If I would write the documentation I would not have
choosen debiandoc sgml.  I'd be happy if somebody would convert this
into XML (I tried in the past but have given up at some point for no
other reason that there are more challenging tasks than fixing XML
syntax.  In any case your documentation should either be part or
integrate into this documentation.

OK my documentation will be part of the blends documentation.
 
 This means you should choose a
format that could be pluged into these doc - or just write right into
the doc if this is accepted by GSoC.  I'd be glad if you could even do
the xml conversion if your time permits.  In any case please make sure
that you will not write some external doc which finally would leave
somebody else to integrate this into blends-doc.

 
OK I will check the documentation in its current format and I will also check/try to make the conversion. In any case the documentation will be integrated into blends-doc.

 
Kind regards

Emmanouil

Reply to: