Hi, preparing my own debian repo for bookworm, I started building and noticed tqt3 is creating ubuntu packages. Seams to be fault in the changelog. I think to remember that I saw someone copied over some files and now we have this entry
tqt-x11-free (3:3.3.8-d-0ubuntu0) maverick; urgency=low
It is so minor issue, but if you want a bug report, let me know.
BR
many other packages are affected the same way
On 2023/07/15 03:59 PM, deloptes via tde-devels wrote:
Hi, preparing my own debian repo for bookworm, I started building and noticed tqt3 is creating ubuntu packages. Seams to be fault in the changelog. I think to remember that I saw someone copied over some files and now we have this entry
tqt-x11-free (3:3.3.8-d-0ubuntu0) maverick; urgency=low
It is so minor issue, but if you want a bug report, let me know.
BR
Hi Emanoil, changelog entries are old and don't get updated in the source code. They are updated at the beginning of the building process or when creating the tarball. Cheers Michele
Michele Calgaro via tde-devels wrote:
On 2023/07/15 03:59 PM, deloptes via tde-devels wrote:
Hi, preparing my own debian repo for bookworm, I started building and noticed tqt3 is creating ubuntu packages. Seams to be fault in the changelog. I think to remember that I saw someone copied over some files and now we have this entry
tqt-x11-free (3:3.3.8-d-0ubuntu0) maverick; urgency=low
It is so minor issue, but if you want a bug report, let me know.
BR
Hi Emanoil, changelog entries are old and don't get updated in the source code. They are updated at the beginning of the building process or when creating the tarball. Cheers Michele
Hi Michele, I know this and it was working for years. I guess bookworm changed dch to request confirmation explicitly when a new entry in changelog is added and it differs from the original. The original seems to be based on ubuntu, so when I ask it to add entry for debian bookworm now, it asks me to confirm.
I solved this by adding the option --force-distribution dch --force-distribution -v ...
There are also some dependencies in packages that need to be carefully examined and updated. I.e. libexif-dev is now libexiv2-dev and alike.
Is here the problem on my end or it is planned to be updated in the repo?
thanks
Hi Michele, I know this and it was working for years. I guess bookworm changed dch to request confirmation explicitly when a new entry in changelog is added and it differs from the original. The original seems to be based on ubuntu, so when I ask it to add entry for debian bookworm now, it asks me to confirm.
I solved this by adding the option --force-distribution dch --force-distribution -v ...
There are also some dependencies in packages that need to be carefully examined and updated. I.e. libexif-dev is now libexiv2-dev and alike.
Is here the problem on my end or it is planned to be updated in the repo?
thanks
Hi Emanoil, not sure about dch, since I edit changelog directly and Slavek's scripts to the same AFAIK, so dch is not used.
Re dependencies, they are usually kept up to date since we build for various distribution versions. I used bookworm for two years when it was "testing" without any major problem in building TDE (now I moved to trixie, or better I stayed on "testing"), so I would start by looking at your end first. Of course if something has changed and dependencies needs to be updated, please let us know.
Cheers Michele
Michele Calgaro via tde-devels wrote:
Hi Emanoil, not sure about dch, since I edit changelog directly and Slavek's scripts to the same AFAIK, so dch is not used.
OK, this explains everything. I use dch to create the required version of changelog on top of the last entry.
Re dependencies, they are usually kept up to date since we build for various distribution versions. I used bookworm for two years when it was "testing" without any major problem in building TDE (now I moved to trixie, or better I stayed on "testing"), so I would start by looking at your end first. Of course if something has changed and dependencies needs to be updated, please let us know.
Well I did not take notes what is missing, but I remember lcm from edeps and few other packages from edeps have python-all requirement which now is python3-all
The next time I build I will take notes and post here
Well I did not take notes what is missing, but I remember lcm from edeps and few other packages from edeps have python-all requirement which now is python3-all
Make sure you always use the latest code. Conversion to python3 was completed 6 months ago and dependencies in tde-packages updated accordingly. Cheers Michele
Michele Calgaro via tde-devels wrote:
Make sure you always use the latest code. Conversion to python3 was completed 6 months ago and dependencies in tde-packages updated accordingly.
Hi Michele, as mentioned it was observed in the edeps. I will review the packages there. I don't remember why for example wv2 is needed and is in there - it could be it missed some debian release.
thanks anyway
deloptes via tde-devels wrote:
Hi, preparing my own debian repo for bookworm, I started building and noticed tqt3 is creating ubuntu packages. Seams to be fault in the changelog. I think to remember that I saw someone copied over some files and now we have this entry
tqt-x11-free (3:3.3.8-d-0ubuntu0) maverick; urgency=low
It is so minor issue, but if you want a bug report, let me know.
BR
I do not see anything in the git log. Could it be that it is resulting from using --stable. dch --stable I added this option because dch started requesting confirmation in bookworm.
thanks in advance BR
I do not see anything in the git log. Could it be that it is resulting from using --stable. dch --stable I added this option because dch started requesting confirmation in bookworm.
thanks in advance BR
In my scripts I edit the changelog when I prepare the source code for building and I believe Slavek does the same for the official packages. There are no entries in git log because there is no update in the original source code as I mentioned in the previous email. Cheers Michele