Hi Bastian, I just realized that I need to make a slight change to file debian/rules by calling dh_auto_configure with an additional argument in order to avoid compiling odr-dabmod with the option "-march=native". Since the odr-dabmod package was not moved to the NEW queue yet, can I just reload the package with the updated debian/rules file or do I also need to modify file debian/changelog indicating the change on debian/rules? In the latter case, do I need to change the package version (ie. moving to 2.6.0-2 from 2.6.0-1)? Have a nice week. -- Robin Le vendredi 29 avril 2022 à 11:14 +0200, Bastian Germann a écrit : > Am 29.04.22 um 11:07 schrieb Robin ALEXANDER: > > As I wrote to you, I: > > 1. Uploaded on Wednesday (April 27) the corrected versions of > > odr- > > dabmux (https://mentors.debian.net/package/odr-dabmux/) and odr- > > dabmod > > (https://mentors.debian.net/package/odr-dabmod/) > > > > 2. Removed the moreinfo tag on odr-dabmux > > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009867) and > > odr- > > dabmod (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010004) > > > > Assuming I did everything correctly, is there anything else I must > > do > > to have these 2 packages pushed to the NEW queue (like what was > > done > > with odr-padenc)? Or is it the sponsor/you who pushes the packages > > to > > the NEW queue by closing the above 2 bugs (1009867 and 1010004) ? > > You just have to wait until someone will review the packages. > My comments were just to help getting the packages to a state where a > DD would have a look at it.
Attachment:
signature.asc
Description: This is a digitally signed message part