Re: Sponsoring of packages for the next stable release
Dear Anton, Just an update on siconos, I used a qemu emulator to run Debian arm64 on my laptop using the OpenStack image as a basis. It took quite a while to build (2 days), and the first attempt of course failed due to time outs, but then I disabled timeouts and the package built and tested, and passed autopkgtest. I am pleasantly surprised. Therefore, I have just pushed another change to disable "ConvexQP_test_collection" which is also a lengthy test, and feel confident that the build should pass on real arm64 hardware. I have marked it as version 4.3.1+dfsg-2 on salsa master. regards, Steve On Mon, Jan 25, 2021 at 10:43 PM Stephen Sinclair wrote: > > I have disabled the test on salsa, but I am not sure the software will > succeed on arm64. Actually I am quite curious, as my attempts to > compile on my Raspberry Pi did not get as far as running that test. > > regards, > Steve > > On Sun, Jan 24, 2021 at 6:39 PM Anton Gladky wrote: > > > > You are welcome! > > > > There is a build problem on arm64 "96 - ContactTest (Timeout)". Please > > fix or disable this > > only test. I have restarted the build but it did not succeed. > > > > Regards > > > > Anton > > > > Am So., 24. Jan. 2021 um 17:54 Uhr schrieb Stephen Sinclair > > : > > > > > > Great, thank you Anton, I don't think I would have figured that out! > > > This should be extremely helpful for future maintenance. > > > > > > regards, > > > Steve
Re: Sponsoring of packages for the next stable release
I have disabled the test on salsa, but I am not sure the software will succeed on arm64. Actually I am quite curious, as my attempts to compile on my Raspberry Pi did not get as far as running that test. regards, Steve On Sun, Jan 24, 2021 at 6:39 PM Anton Gladky wrote: > > You are welcome! > > There is a build problem on arm64 "96 - ContactTest (Timeout)". Please > fix or disable this > only test. I have restarted the build but it did not succeed. > > Regards > > Anton > > Am So., 24. Jan. 2021 um 17:54 Uhr schrieb Stephen Sinclair > : > > > > Great, thank you Anton, I don't think I would have figured that out! This > > should be extremely helpful for future maintenance. > > > > regards, > > Steve
Re: Sponsoring of packages for the next stable release
You are welcome! There is a build problem on arm64 "96 - ContactTest (Timeout)". Please fix or disable this only test. I have restarted the build but it did not succeed. Regards Anton Am So., 24. Jan. 2021 um 17:54 Uhr schrieb Stephen Sinclair : > > Great, thank you Anton, I don't think I would have figured that out! This > should be extremely helpful for future maintenance. > > regards, > Steve
Re: Sponsoring of packages for the next stable release
Great, thank you Anton, I don't think I would have figured that out! This should be extremely helpful for future maintenance. regards, Steve On Sat, Jan 23, 2021, 10:27 PM Anton Gladky wrote: > Hi Stephen, > > I have disabled i386 build [1] and reduced the size of salsa-build > binaries [2]. > Now it builds fine in pipeline and I have uploaded the package. > > [1] > https://salsa.debian.org/science-team/siconos/-/commit/8aca640c2743655e87aa181ddfd153f51e6f58e7 > [2] > https://salsa.debian.org/science-team/siconos/-/commit/9a836cee37a46e20721ab33871f55b54e6e953dc > > Best regards > > Anton > > Am Sa., 23. Jan. 2021 um 14:48 Uhr schrieb Stephen Sinclair > : > > > > Hi Anton, > > > > Thanks, last time I tried to use the salsa pipeline for this package, > > it was not possible because the build produced too much log output and > > failed for that reason. > > It seems that in your attempt, it actually makes it all the way to the > > end; I'm actually not clear on what "fails", it actually succeeds > > building and testing the package, but ends with, > > > > > Uploading artifacts as "archive" to coordinator... failed > > > context=artifacts-uploader error=invalid argument > > > > I have no idea what arguments to what program are invalid here, but it > > seems to have to do with the pipeline process and not the package > > itself. > > > > https://salsa.debian.org/science-team/siconos/-/jobs/1367137 > > > > For the i386 build, it fails unfortunately simply because the machine > > runs out of memory. (The build annoyingly requires upwards of 7 GB of > > memory while compiling the SWIG bindings; part of the motivation for > > wanting to distribute a pre-compiled package!) However to be honest I > > am not sure siconos works properly on 32-bit architectures anyway. > > https://salsa.debian.org/science-team/siconos/-/jobs/1367138 > > > > As for other architectures, there is a bug on arm64 that I have been > > trying to fix but it is not an easy one. In the meantime the package > > is very useful for x86_64 users, who are in the majority. > > > > regards, > > Steve > > > > On Fri, Jan 22, 2021 at 10:36 PM Anton Gladky wrote: > > > > > > Hi Stephen, > > > > > > I have enabled the salsa-pipeline on siconos package and it seems > > > fails to build currently [1]. Could you please take a look and let me > know, > > > whether it is ready to be uploaded. > > > > > > Thanks > > > > > > [1] https://salsa.debian.org/science-team/siconos/-/pipelines > > > > > > Anton > > > > > > Am Mi., 20. Jan. 2021 um 22:46 Uhr schrieb Stephen Sinclair > > > : > > > > > > > > Hello, > > > > > > > > If there still is time, there is a minor version upstream update to > > > > the siconos package looking for a sponsor: > > > > https://mentors.debian.net/package/siconos/ > > > > > > > > siconos (4.3.1+dfsg-1) unstable; urgency=medium > > > > . > > > >* New upstream release. > > > >* Rebase patches: > > > > + Remove upstreamed patch to FindLAPACK.cmake. > > > >* Update policy version 4.5.1. > > > >* Update debhelper version 13. > > > >* Add missing symbols for numerics. > > > >* Change architecture for siconos and siconos-mechanics-tools to > all. > > > >* Add debian/upstream/metadata. > > > >* Replace debian/compat with debhelper-compat package. > > > > > > > > > > > > regards, > > > > Steve > > > > > > > > On Sat, Jan 9, 2021 at 9:27 PM Anton Gladky > wrote: > > > > > > > > > > Dear members of Debian Science Team, > > > > > > > > > > we are approaching to a new stable release freeze. If youhave some > > > > > packages to be sponsored, please let us know. > > > > > > > > > > I have a very limited time, but I will try to review/sponsor someof > > > > > packages. > > > > > > > > > > > > > > > Best regards > > > > > > > > > > Anton > > > > > >
Re: Sponsoring of packages for the next stable release
Hi Stephen, I have disabled i386 build [1] and reduced the size of salsa-build binaries [2]. Now it builds fine in pipeline and I have uploaded the package. [1] https://salsa.debian.org/science-team/siconos/-/commit/8aca640c2743655e87aa181ddfd153f51e6f58e7 [2] https://salsa.debian.org/science-team/siconos/-/commit/9a836cee37a46e20721ab33871f55b54e6e953dc Best regards Anton Am Sa., 23. Jan. 2021 um 14:48 Uhr schrieb Stephen Sinclair : > > Hi Anton, > > Thanks, last time I tried to use the salsa pipeline for this package, > it was not possible because the build produced too much log output and > failed for that reason. > It seems that in your attempt, it actually makes it all the way to the > end; I'm actually not clear on what "fails", it actually succeeds > building and testing the package, but ends with, > > > Uploading artifacts as "archive" to coordinator... failed > > context=artifacts-uploader error=invalid argument > > I have no idea what arguments to what program are invalid here, but it > seems to have to do with the pipeline process and not the package > itself. > > https://salsa.debian.org/science-team/siconos/-/jobs/1367137 > > For the i386 build, it fails unfortunately simply because the machine > runs out of memory. (The build annoyingly requires upwards of 7 GB of > memory while compiling the SWIG bindings; part of the motivation for > wanting to distribute a pre-compiled package!) However to be honest I > am not sure siconos works properly on 32-bit architectures anyway. > https://salsa.debian.org/science-team/siconos/-/jobs/1367138 > > As for other architectures, there is a bug on arm64 that I have been > trying to fix but it is not an easy one. In the meantime the package > is very useful for x86_64 users, who are in the majority. > > regards, > Steve > > On Fri, Jan 22, 2021 at 10:36 PM Anton Gladky wrote: > > > > Hi Stephen, > > > > I have enabled the salsa-pipeline on siconos package and it seems > > fails to build currently [1]. Could you please take a look and let me know, > > whether it is ready to be uploaded. > > > > Thanks > > > > [1] https://salsa.debian.org/science-team/siconos/-/pipelines > > > > Anton > > > > Am Mi., 20. Jan. 2021 um 22:46 Uhr schrieb Stephen Sinclair > > : > > > > > > Hello, > > > > > > If there still is time, there is a minor version upstream update to > > > the siconos package looking for a sponsor: > > > https://mentors.debian.net/package/siconos/ > > > > > > siconos (4.3.1+dfsg-1) unstable; urgency=medium > > > . > > >* New upstream release. > > >* Rebase patches: > > > + Remove upstreamed patch to FindLAPACK.cmake. > > >* Update policy version 4.5.1. > > >* Update debhelper version 13. > > >* Add missing symbols for numerics. > > >* Change architecture for siconos and siconos-mechanics-tools to all. > > >* Add debian/upstream/metadata. > > >* Replace debian/compat with debhelper-compat package. > > > > > > > > > regards, > > > Steve > > > > > > On Sat, Jan 9, 2021 at 9:27 PM Anton Gladky wrote: > > > > > > > > Dear members of Debian Science Team, > > > > > > > > we are approaching to a new stable release freeze. If youhave some > > > > packages to be sponsored, please let us know. > > > > > > > > I have a very limited time, but I will try to review/sponsor someof > > > > packages. > > > > > > > > > > > > Best regards > > > > > > > > Anton > > > >
Re: Sponsoring of packages for the next stable release
Hi Anton, Thanks, last time I tried to use the salsa pipeline for this package, it was not possible because the build produced too much log output and failed for that reason. It seems that in your attempt, it actually makes it all the way to the end; I'm actually not clear on what "fails", it actually succeeds building and testing the package, but ends with, > Uploading artifacts as "archive" to coordinator... failed > context=artifacts-uploader error=invalid argument I have no idea what arguments to what program are invalid here, but it seems to have to do with the pipeline process and not the package itself. https://salsa.debian.org/science-team/siconos/-/jobs/1367137 For the i386 build, it fails unfortunately simply because the machine runs out of memory. (The build annoyingly requires upwards of 7 GB of memory while compiling the SWIG bindings; part of the motivation for wanting to distribute a pre-compiled package!) However to be honest I am not sure siconos works properly on 32-bit architectures anyway. https://salsa.debian.org/science-team/siconos/-/jobs/1367138 As for other architectures, there is a bug on arm64 that I have been trying to fix but it is not an easy one. In the meantime the package is very useful for x86_64 users, who are in the majority. regards, Steve On Fri, Jan 22, 2021 at 10:36 PM Anton Gladky wrote: > > Hi Stephen, > > I have enabled the salsa-pipeline on siconos package and it seems > fails to build currently [1]. Could you please take a look and let me know, > whether it is ready to be uploaded. > > Thanks > > [1] https://salsa.debian.org/science-team/siconos/-/pipelines > > Anton > > Am Mi., 20. Jan. 2021 um 22:46 Uhr schrieb Stephen Sinclair > : > > > > Hello, > > > > If there still is time, there is a minor version upstream update to > > the siconos package looking for a sponsor: > > https://mentors.debian.net/package/siconos/ > > > > siconos (4.3.1+dfsg-1) unstable; urgency=medium > > . > >* New upstream release. > >* Rebase patches: > > + Remove upstreamed patch to FindLAPACK.cmake. > >* Update policy version 4.5.1. > >* Update debhelper version 13. > >* Add missing symbols for numerics. > >* Change architecture for siconos and siconos-mechanics-tools to all. > >* Add debian/upstream/metadata. > >* Replace debian/compat with debhelper-compat package. > > > > > > regards, > > Steve > > > > On Sat, Jan 9, 2021 at 9:27 PM Anton Gladky wrote: > > > > > > Dear members of Debian Science Team, > > > > > > we are approaching to a new stable release freeze. If youhave some > > > packages to be sponsored, please let us know. > > > > > > I have a very limited time, but I will try to review/sponsor someof > > > packages. > > > > > > > > > Best regards > > > > > > Anton > > >
Re: Sponsoring of packages for the next stable release
Hi Stephen, I have enabled the salsa-pipeline on siconos package and it seems fails to build currently [1]. Could you please take a look and let me know, whether it is ready to be uploaded. Thanks [1] https://salsa.debian.org/science-team/siconos/-/pipelines Anton Am Mi., 20. Jan. 2021 um 22:46 Uhr schrieb Stephen Sinclair : > > Hello, > > If there still is time, there is a minor version upstream update to > the siconos package looking for a sponsor: > https://mentors.debian.net/package/siconos/ > > siconos (4.3.1+dfsg-1) unstable; urgency=medium > . >* New upstream release. >* Rebase patches: > + Remove upstreamed patch to FindLAPACK.cmake. >* Update policy version 4.5.1. >* Update debhelper version 13. >* Add missing symbols for numerics. >* Change architecture for siconos and siconos-mechanics-tools to all. >* Add debian/upstream/metadata. >* Replace debian/compat with debhelper-compat package. > > > regards, > Steve > > On Sat, Jan 9, 2021 at 9:27 PM Anton Gladky wrote: > > > > Dear members of Debian Science Team, > > > > we are approaching to a new stable release freeze. If youhave some > > packages to be sponsored, please let us know. > > > > I have a very limited time, but I will try to review/sponsor someof > > packages. > > > > > > Best regards > > > > Anton > >
Re: Sponsoring of packages for the next stable release
- 3.0.rc2+repack1-1 is on https://salsa.debian.org/science-team/solvespace and ready for upload to unstable: I removed the autopkgtests because they were breaking the CI at the moment. This should fix the FTBFS on armel, I think/hope, and also brings the code up to the new release version, updates the exclusion list and copyright file, etc. - I added back the autopkgtests in this MR: https://salsa.debian.org/science-team/solvespace/-/merge_requests/1 I'm not sure why it's failing, help appreciated. - I have a release after 3.0.rc2+repack1-1 (I added +exp1) to add LTO and OpenMP, this can be reviewed and released to experimental after unstable receives their upload. https://salsa.debian.org/science-team/solvespace/-/merge_requests/2 Thanks for your help! Ryan On 1/21/2021 2:05 PM, Anton Gladky wrote: > Thanks a lot for update. Please prepare a merge request, let's check > the pipelines and I will upload > it into the experimental. > > Best regards > > Anton > > Am Do., 21. Jan. 2021 um 18:10 Uhr schrieb Ryan Pavlik > : >> Update: I re-did it calling it 3.0.rc2+repack1 since the ~ ended up >> breaking piuparts on CI. It's just a minor detail in the scheme of >> things, I assume. I have pushed to the team repo. >> >> It should be "safe" to release now. There is new support for OpenMP and >> LTO, but without direct access to experimental and buildd's of the >> various architectures, I wouldn't want to upload a package to unstable >> at this point with those enabled and risk breaking it. It works fine, if >> a smidge slower than possible, without openmp and LTO enabled, so I >> think probably leave it well enough alone. >> >> I've added some autopkgtests using the CLI interface as completely as >> possible without modifying the source tree, which should help too. >> Probably the most fragile part of the package is the use of three-js >> (libjs-three) for the HTML trimesh viewer export: if that gets updated >> and breaks something being used, the export will appear to work fine but >> will hit a javascript error on usage. I'd be interested to learn how to >> write up the test to catch this, if anybody has ideas. >> >> Thanks! >> >> Ryan >> >> On 1/19/2021 5:57 PM, Ryan Pavlik wrote: >>> Anton, >>> >>> Thanks for taking the time to update that package! Upstream has released >>> another RC (which should be identical to 3.0 with the exception of >>> translation updates). Additionally, we've found a patch from upstream >>> mimalloc that should fix the armel build (I hope), and which I have >>> included in the debian package. I have updated to that upstream release, >>> and updated the package substantially (removed some bundled fonts and >>> js, etc) and pushed to my salsa repo: I wasn't sure if you wanted me to >>> push to the main team repo, especially since the existing version is >>> "3.0.rc1+repack1" which Lintian warns me is not less than 3.0 - I did my >>> import as "3.0~rc2+repack1" accordingly. >>> >>> https://salsa.debian.org/rpavlik/solvespace >>> >>> When you have a chance, I'd appreciate a review and sponsoring. I've >>> done basic testing of the package myself, especially the parts that are >>> affected by patches/repack, and it seems to work well to me. >>> >>> Thanks! >>> >>> Ryan >>> >>> On 1/16/2021 12:09 PM, Anton Gladky wrote: Hi Ryan, the newer version of solvespace is in sid already. There is a problem with armel compilation selected processor does not support `yield' in ARM mode So I requested the removal of the package on this platform. If somebody has an advice how to fix this special assembler-problem, please let me know. Best regards Anton Anton Am Do., 14. Jan. 2021 um 00:33 Uhr schrieb Ryan Pavlik : > On 1/9/2021 2:27 PM, Anton Gladky wrote: >> Dear members of Debian Science Team, >> >> we are approaching to a new stable release freeze. If youhave some >> packages to be sponsored, please let us know. >> >> I have a very limited time, but I will try to review/sponsor someof >> packages. >> >> >> Best regards >> >> Anton > I see you were the last to touch the SolveSpace package. Do you expect > to have time to look at that soon to update to the new RC? (They/we have > very high stability standards, 3.0 could have been released 2 years ago) > If not, I'll go ahead and update to the latest tagged upstream this week > and request sponsorship. > > > Thanks, > > > Ryan > > signature.asc Description: OpenPGP digital signature
Re: Sponsoring of packages for the next stable release
Thanks a lot for update. Please prepare a merge request, let's check the pipelines and I will upload it into the experimental. Best regards Anton Am Do., 21. Jan. 2021 um 18:10 Uhr schrieb Ryan Pavlik : > > Update: I re-did it calling it 3.0.rc2+repack1 since the ~ ended up > breaking piuparts on CI. It's just a minor detail in the scheme of > things, I assume. I have pushed to the team repo. > > It should be "safe" to release now. There is new support for OpenMP and > LTO, but without direct access to experimental and buildd's of the > various architectures, I wouldn't want to upload a package to unstable > at this point with those enabled and risk breaking it. It works fine, if > a smidge slower than possible, without openmp and LTO enabled, so I > think probably leave it well enough alone. > > I've added some autopkgtests using the CLI interface as completely as > possible without modifying the source tree, which should help too. > Probably the most fragile part of the package is the use of three-js > (libjs-three) for the HTML trimesh viewer export: if that gets updated > and breaks something being used, the export will appear to work fine but > will hit a javascript error on usage. I'd be interested to learn how to > write up the test to catch this, if anybody has ideas. > > Thanks! > > Ryan > > On 1/19/2021 5:57 PM, Ryan Pavlik wrote: > > Anton, > > > > Thanks for taking the time to update that package! Upstream has released > > another RC (which should be identical to 3.0 with the exception of > > translation updates). Additionally, we've found a patch from upstream > > mimalloc that should fix the armel build (I hope), and which I have > > included in the debian package. I have updated to that upstream release, > > and updated the package substantially (removed some bundled fonts and > > js, etc) and pushed to my salsa repo: I wasn't sure if you wanted me to > > push to the main team repo, especially since the existing version is > > "3.0.rc1+repack1" which Lintian warns me is not less than 3.0 - I did my > > import as "3.0~rc2+repack1" accordingly. > > > > https://salsa.debian.org/rpavlik/solvespace > > > > When you have a chance, I'd appreciate a review and sponsoring. I've > > done basic testing of the package myself, especially the parts that are > > affected by patches/repack, and it seems to work well to me. > > > > Thanks! > > > > Ryan > > > > On 1/16/2021 12:09 PM, Anton Gladky wrote: > >> Hi Ryan, > >> > >> the newer version of solvespace is in sid already. There is a problem > >> with armel compilation > >> > >> selected processor does not support `yield' in ARM mode > >> > >> So I requested the removal of the package on this platform. > >> If somebody has an advice how to fix this special assembler-problem, > >> please let me know. > >> > >> Best regards > >> > >> Anton > >> > >> > >> Anton > >> > >> > >> Am Do., 14. Jan. 2021 um 00:33 Uhr schrieb Ryan Pavlik > >> : > >>> On 1/9/2021 2:27 PM, Anton Gladky wrote: > Dear members of Debian Science Team, > > we are approaching to a new stable release freeze. If youhave some > packages to be sponsored, please let us know. > > I have a very limited time, but I will try to review/sponsor someof > packages. > > > Best regards > > Anton > >>> I see you were the last to touch the SolveSpace package. Do you expect > >>> to have time to look at that soon to update to the new RC? (They/we have > >>> very high stability standards, 3.0 could have been released 2 years ago) > >>> If not, I'll go ahead and update to the latest tagged upstream this week > >>> and request sponsorship. > >>> > >>> > >>> Thanks, > >>> > >>> > >>> Ryan > >>> > >>> >
Re: Sponsoring of packages for the next stable release
Update: I re-did it calling it 3.0.rc2+repack1 since the ~ ended up breaking piuparts on CI. It's just a minor detail in the scheme of things, I assume. I have pushed to the team repo. It should be "safe" to release now. There is new support for OpenMP and LTO, but without direct access to experimental and buildd's of the various architectures, I wouldn't want to upload a package to unstable at this point with those enabled and risk breaking it. It works fine, if a smidge slower than possible, without openmp and LTO enabled, so I think probably leave it well enough alone. I've added some autopkgtests using the CLI interface as completely as possible without modifying the source tree, which should help too. Probably the most fragile part of the package is the use of three-js (libjs-three) for the HTML trimesh viewer export: if that gets updated and breaks something being used, the export will appear to work fine but will hit a javascript error on usage. I'd be interested to learn how to write up the test to catch this, if anybody has ideas. Thanks! Ryan On 1/19/2021 5:57 PM, Ryan Pavlik wrote: > Anton, > > Thanks for taking the time to update that package! Upstream has released > another RC (which should be identical to 3.0 with the exception of > translation updates). Additionally, we've found a patch from upstream > mimalloc that should fix the armel build (I hope), and which I have > included in the debian package. I have updated to that upstream release, > and updated the package substantially (removed some bundled fonts and > js, etc) and pushed to my salsa repo: I wasn't sure if you wanted me to > push to the main team repo, especially since the existing version is > "3.0.rc1+repack1" which Lintian warns me is not less than 3.0 - I did my > import as "3.0~rc2+repack1" accordingly. > > https://salsa.debian.org/rpavlik/solvespace > > When you have a chance, I'd appreciate a review and sponsoring. I've > done basic testing of the package myself, especially the parts that are > affected by patches/repack, and it seems to work well to me. > > Thanks! > > Ryan > > On 1/16/2021 12:09 PM, Anton Gladky wrote: >> Hi Ryan, >> >> the newer version of solvespace is in sid already. There is a problem >> with armel compilation >> >> selected processor does not support `yield' in ARM mode >> >> So I requested the removal of the package on this platform. >> If somebody has an advice how to fix this special assembler-problem, >> please let me know. >> >> Best regards >> >> Anton >> >> >> Anton >> >> >> Am Do., 14. Jan. 2021 um 00:33 Uhr schrieb Ryan Pavlik >> : >>> On 1/9/2021 2:27 PM, Anton Gladky wrote: Dear members of Debian Science Team, we are approaching to a new stable release freeze. If youhave some packages to be sponsored, please let us know. I have a very limited time, but I will try to review/sponsor someof packages. Best regards Anton >>> I see you were the last to touch the SolveSpace package. Do you expect >>> to have time to look at that soon to update to the new RC? (They/we have >>> very high stability standards, 3.0 could have been released 2 years ago) >>> If not, I'll go ahead and update to the latest tagged upstream this week >>> and request sponsorship. >>> >>> >>> Thanks, >>> >>> >>> Ryan >>> >>> signature.asc Description: OpenPGP digital signature
Re: Sponsoring of packages for the next stable release
Hello, If there still is time, there is a minor version upstream update to the siconos package looking for a sponsor: https://mentors.debian.net/package/siconos/ siconos (4.3.1+dfsg-1) unstable; urgency=medium . * New upstream release. * Rebase patches: + Remove upstreamed patch to FindLAPACK.cmake. * Update policy version 4.5.1. * Update debhelper version 13. * Add missing symbols for numerics. * Change architecture for siconos and siconos-mechanics-tools to all. * Add debian/upstream/metadata. * Replace debian/compat with debhelper-compat package. regards, Steve On Sat, Jan 9, 2021 at 9:27 PM Anton Gladky wrote: > > Dear members of Debian Science Team, > > we are approaching to a new stable release freeze. If youhave some > packages to be sponsored, please let us know. > > I have a very limited time, but I will try to review/sponsor someof > packages. > > > Best regards > > Anton >
Re: Sponsoring of packages for the next stable release
Anton, Thanks for taking the time to update that package! Upstream has released another RC (which should be identical to 3.0 with the exception of translation updates). Additionally, we've found a patch from upstream mimalloc that should fix the armel build (I hope), and which I have included in the debian package. I have updated to that upstream release, and updated the package substantially (removed some bundled fonts and js, etc) and pushed to my salsa repo: I wasn't sure if you wanted me to push to the main team repo, especially since the existing version is "3.0.rc1+repack1" which Lintian warns me is not less than 3.0 - I did my import as "3.0~rc2+repack1" accordingly. https://salsa.debian.org/rpavlik/solvespace When you have a chance, I'd appreciate a review and sponsoring. I've done basic testing of the package myself, especially the parts that are affected by patches/repack, and it seems to work well to me. Thanks! Ryan On 1/16/2021 12:09 PM, Anton Gladky wrote: > Hi Ryan, > > the newer version of solvespace is in sid already. There is a problem > with armel compilation > > selected processor does not support `yield' in ARM mode > > So I requested the removal of the package on this platform. > If somebody has an advice how to fix this special assembler-problem, > please let me know. > > Best regards > > Anton > > > Anton > > > Am Do., 14. Jan. 2021 um 00:33 Uhr schrieb Ryan Pavlik > : >> >> On 1/9/2021 2:27 PM, Anton Gladky wrote: >>> Dear members of Debian Science Team, >>> >>> we are approaching to a new stable release freeze. If youhave some >>> packages to be sponsored, please let us know. >>> >>> I have a very limited time, but I will try to review/sponsor someof >>> packages. >>> >>> >>> Best regards >>> >>> Anton >> >> I see you were the last to touch the SolveSpace package. Do you expect >> to have time to look at that soon to update to the new RC? (They/we have >> very high stability standards, 3.0 could have been released 2 years ago) >> If not, I'll go ahead and update to the latest tagged upstream this week >> and request sponsorship. >> >> >> Thanks, >> >> >> Ryan >> >>
Re: Sponsoring of packages for the next stable release
Hi Ryan, the newer version of solvespace is in sid already. There is a problem with armel compilation selected processor does not support `yield' in ARM mode So I requested the removal of the package on this platform. If somebody has an advice how to fix this special assembler-problem, please let me know. Best regards Anton Anton Am Do., 14. Jan. 2021 um 00:33 Uhr schrieb Ryan Pavlik : > > > On 1/9/2021 2:27 PM, Anton Gladky wrote: > > Dear members of Debian Science Team, > > > > we are approaching to a new stable release freeze. If youhave some > > packages to be sponsored, please let us know. > > > > I have a very limited time, but I will try to review/sponsor someof > > packages. > > > > > > Best regards > > > > Anton > > > I see you were the last to touch the SolveSpace package. Do you expect > to have time to look at that soon to update to the new RC? (They/we have > very high stability standards, 3.0 could have been released 2 years ago) > If not, I'll go ahead and update to the latest tagged upstream this week > and request sponsorship. > > > Thanks, > > > Ryan > >
Re: Sponsoring of packages for the next stable release
On 1/9/2021 2:27 PM, Anton Gladky wrote: > Dear members of Debian Science Team, > > we are approaching to a new stable release freeze. If youhave some > packages to be sponsored, please let us know. > > I have a very limited time, but I will try to review/sponsor someof > packages. > > > Best regards > > Anton I see you were the last to touch the SolveSpace package. Do you expect to have time to look at that soon to update to the new RC? (They/we have very high stability standards, 3.0 could have been released 2 years ago) If not, I'll go ahead and update to the latest tagged upstream this week and request sponsorship. Thanks, Ryan signature.asc Description: OpenPGP digital signature
Sponsoring of packages for the next stable release
Dear members of Debian Science Team, we are approaching to a new stable release freeze. If youhave some packages to be sponsored, please let us know. I have a very limited time, but I will try to review/sponsor someof packages. Best regards Anton OpenPGP_signature Description: OpenPGP digital signature
