Bug#957037: biboumi: ftbfs with GCC-10
Michel Le Bihan writes: > Hello, > > I opened a merge request, but merging all branches into your repo > might cause issues in the upstream branch in the future due to the > merge commits. Instead, it will be best to pull all branches from my > repo into branches of your repo, but without adding merge commits or > at least without adding them to the upstream and pristine tar > branches. Thank you I've given some review comments, please incorporate them. I think merging all branches will not cause any problems, I've done in simiar way for bpfcc-tools as well. Cheers, Vasudev
Bug#957037: biboumi: ftbfs with GCC-10
Hello, I opened a merge request, but merging all branches into your repo might cause issues in the upstream branch in the future due to the merge commits. Instead, it will be best to pull all branches from my repo into branches of your repo, but without adding merge commits or at least without adding them to the upstream and pristine tar branches. Michel Le Bihan Le 23 décembre 2020 04:58:21 GMT+01:00, Vasudev Kamath a écrit : >Michel Le Bihan writes: > >> Le mardi 22 décembre 2020 à 17:35 +0530, Vasudev Kamath a écrit : >>> Jonas Smedegaard writes: >>> >>> > Quoting Michel Le Bihan (2020-12-20 17:15:29) >>> > > Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a >>> > > écrit : >>> > > > Quoting Michel Le Bihan (2020-12-20 16:06:27) >>> > > > > A quick summary of the differences between both repos: >>> > > > >>> > > > Thanks, that is no doubt helpful! >>> > > > >>> > > > [ beware: commenting without actually having looked at the >>> > > > code! ] >>> > > Please look at it when you will have time. >>> > >>> > Most likely no: Instead, please wait for Vasudev to look at it. >>> >>> I was looking at biboumi repository and did not see any merge >>> requests >>> on it. Jonas do we need to enable something in repo to allow merge >>> requests?. >>> >> Yes. You need to enable merge requests in the repository settings. They >> are currently disabled. > >Done, it took me a while to navigate around the settings. Please raise >MR so I can review. > >Cheers, >Vasudev
Bug#957037: biboumi: ftbfs with GCC-10
Michel Le Bihan writes: > Le mardi 22 décembre 2020 à 17:35 +0530, Vasudev Kamath a écrit : >> Jonas Smedegaard writes: >> >> > Quoting Michel Le Bihan (2020-12-20 17:15:29) >> > > Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a >> > > écrit : >> > > > Quoting Michel Le Bihan (2020-12-20 16:06:27) >> > > > > A quick summary of the differences between both repos: >> > > > >> > > > Thanks, that is no doubt helpful! >> > > > >> > > > [ beware: commenting without actually having looked at the >> > > > code! ] >> > > Please look at it when you will have time. >> > >> > Most likely no: Instead, please wait for Vasudev to look at it. >> >> I was looking at biboumi repository and did not see any merge >> requests >> on it. Jonas do we need to enable something in repo to allow merge >> requests?. >> > Yes. You need to enable merge requests in the repository settings. They > are currently disabled. Done, it took me a while to navigate around the settings. Please raise MR so I can review. Cheers, Vasudev
Bug#957037: biboumi: ftbfs with GCC-10
Le mardi 22 décembre 2020 à 17:35 +0530, Vasudev Kamath a écrit : > Jonas Smedegaard writes: > > > Quoting Michel Le Bihan (2020-12-20 17:15:29) > > > Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a > > > écrit : > > > > Quoting Michel Le Bihan (2020-12-20 16:06:27) > > > > > A quick summary of the differences between both repos: > > > > > > > > Thanks, that is no doubt helpful! > > > > > > > > [ beware: commenting without actually having looked at the > > > > code! ] > > > Please look at it when you will have time. > > > > Most likely no: Instead, please wait for Vasudev to look at it. > > I was looking at biboumi repository and did not see any merge > requests > on it. Jonas do we need to enable something in repo to allow merge > requests?. > Yes. You need to enable merge requests in the repository settings. They are currently disabled. > @Michel/Alberto it would be great if you can raise a merge request. > It > will be easier for me to look at the changes faster. > > > > > > > > Now that you joined the team maintaining the package, it is not > > > > an > > > > NMU. > > > > > > > Should I change that? Somebody would have to add me to > > > debian/control, > > > but I don't want to rebase my fork on that commit for that > > > change. > > > > My point was more general about when that annotation was needed. > > > > I'll leave the details of handling this concrete changeset to > > Vasudev. > > > > You can add yourself to debian/control and commit that changes. No > need > for waiting for some one else to add you there :-). > > Please keep me in Cc I might miss the mails otherwise. > > Cheers, > Vasudev
Bug#957037: biboumi: ftbfs with GCC-10
Jonas Smedegaard writes: > Quoting Michel Le Bihan (2020-12-20 17:15:29) >> Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a écrit : >> > Quoting Michel Le Bihan (2020-12-20 16:06:27) >> > > A quick summary of the differences between both repos: >> > >> > Thanks, that is no doubt helpful! >> > >> > [ beware: commenting without actually having looked at the code! ] >> Please look at it when you will have time. > > Most likely no: Instead, please wait for Vasudev to look at it. I was looking at biboumi repository and did not see any merge requests on it. Jonas do we need to enable something in repo to allow merge requests?. @Michel/Alberto it would be great if you can raise a merge request. It will be easier for me to look at the changes faster. > > >> > Now that you joined the team maintaining the package, it is not an >> > NMU. >> > >> Should I change that? Somebody would have to add me to debian/control, >> but I don't want to rebase my fork on that commit for that change. > > My point was more general about when that annotation was needed. > > I'll leave the details of handling this concrete changeset to Vasudev. > You can add yourself to debian/control and commit that changes. No need for waiting for some one else to add you there :-). Please keep me in Cc I might miss the mails otherwise. Cheers, Vasudev
Bug#957037: biboumi: ftbfs with GCC-10
Quoting Michel Le Bihan (2020-12-20 17:15:29) > Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a écrit : > > Quoting Michel Le Bihan (2020-12-20 16:06:27) > > > A quick summary of the differences between both repos: > > > > Thanks, that is no doubt helpful! > > > > [ beware: commenting without actually having looked at the code! ] > Please look at it when you will have time. Most likely no: Instead, please wait for Vasudev to look at it. > > Now that you joined the team maintaining the package, it is not an > > NMU. > > > Should I change that? Somebody would have to add me to debian/control, > but I don't want to rebase my fork on that commit for that change. My point was more general about when that annotation was needed. I'll leave the details of handling this concrete changeset to Vasudev. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#957037: biboumi: ftbfs with GCC-10
[ replying to bugreport - please keep conversation public ] Quoting Michel Le Bihan (2020-12-20 16:57:36) > Yes. I wasn't able to find doc on that on my own. tarpman and wRAR > from #debian-mentors helped me with that and pointed me to > file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.upstream- > git.html#gbp.import.upstream.git.tarball Thanks for (sort of) confirming that such usage comment might be of help. I will continue my practice of adding it to packages I maintain. > I actually used: > ``` > git remote add upstream https://lab.louiz.org/louiz/biboumi.git > git fetch upstream > gbp import-orig --pristine-tar --upstream-vcs-tag=9.0 > https://lab.louiz.org/louiz/biboumi/-/archive/9.0/biboumi-9.0.tar.bz2 > ``` Thanks for sharing. Your commands lead to same result in the git shared among maintainers, so not bad. My command is shorter (option --pristine-tar is already defined in config file) and smarter (option --uscan resolved upstream tarball URL from the watch file hint): gbp import-orig --upstream-vcs-tag=9.0 --uscan Also, beware that naming the _remote_ "upstream" is easily confused with _branch_ name "upstream" (or the recommended branch name "upstream/latest" not yet used in biboumi package - see https://dep-team.pages.debian.net/deps/dep14/ ). I name it "upstream-git" to disambiguate. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#957037: biboumi: ftbfs with GCC-10
Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a écrit : > Quoting Michel Le Bihan (2020-12-20 16:06:27) > > A quick summary of the differences between both repos: > > Thanks, that is no doubt helpful! > > [ beware: commenting without actually having looked at the code! ] Please look at it when you will have time. > > > 2. Aluaces package might be missing man pages. Upstream is now > > using > > Sphinx instead of Pandoc. I added a patch to build man and updated > > control. They put doc/*.rst in examples and I put it in doc. > > > I also moved the new example config to `/etc/biboumi/biboumi.cfg` > > since most packages install example config directly in their final > > location in `/etc`. > > If "sample" config files are working out of the box then good - > otherwise not. > > > > 3. I updated copyright hints. > > Only update copyright_hints if you update copyright file as needed - > otherwise better that you do *not* update copyright_hints: The hints > file being out of sync is a way to recognize that copyright file is > pending a closer examination. > New doc location, tests added and some source files. In my opinion that does not require an update to the copyright file, but I ack the changes. > > > 4. My release is marked NMU. > > Now that you joined the team maintaining the package, it is not an > NMU. > Should I change that? Somebody would have to add me to debian/control, but I don't want to rebase my fork on that commit for that change. > > - Jonas >
Bug#957037: biboumi: ftbfs with GCC-10
Quoting Michel Le Bihan (2020-12-20 16:06:27) > A quick summary of the differences between both repos: Thanks, that is no doubt helpful! [ beware: commenting without actually having looked at the code! ] > 2. Aluaces package might be missing man pages. Upstream is now using > Sphinx instead of Pandoc. I added a patch to build man and updated > control. They put doc/*.rst in examples and I put it in doc. > I also moved the new example config to `/etc/biboumi/biboumi.cfg` > since most packages install example config directly in their final > location in `/etc`. If "sample" config files are working out of the box then good - otherwise not. > 3. I updated copyright hints. Only update copyright_hints if you update copyright file as needed - otherwise better that you do *not* update copyright_hints: The hints file being out of sync is a way to recognize that copyright file is pending a closer examination. > 4. My release is marked NMU. Now that you joined the team maintaining the package, it is not an NMU. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#957037: biboumi: ftbfs with GCC-10
Quoting Michel Le Bihan (2020-12-20 12:06:44) > It took me some time to understand how source of this package is > imported in the Salsa repo, I didn't look (still too busy elsewhere, please wait for Vadudev), just wanted to share what I have begun adding to packages that I maintain: https://salsa.debian.org/pkg-voip-team/baresip/-/commit/fee2f7f Would such usage comment have been a help in your struggle, if it had been in the biboumi package (and you had stumbled upon it, obviously)? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#957037: biboumi: ftbfs with GCC-10
A quick summary of the differences between both repos: 1. Source is imported differently. I tried to import source the same way it was done previously. 2. Aluaces package might be missing man pages. Upstream is now using Sphinx instead of Pandoc. I added a patch to build man and updated control. They put doc/*.rst in examples and I put it in doc. I also moved the new example config to `/etc/biboumi/biboumi.cfg` since most packages install example config directly in their final location in `/etc`. 3. I updated copyright hints. 4. My release is marked NMU. Michel Le Bihan Le dimanche 20 décembre 2020 à 15:30 +0100, Jonas Smedegaard a écrit : > Quoting Vasudev Kamath (2020-12-15 09:35:35) > > > > Hi Alberto, > > > > > I have checked that current upstream (9.0) builds flawlessly, and > > > made my release available at > > > https://salsa.debian.org/aluaces-guest/biboumi . > > > > That is great. > > > > > Can I be sponsored so we can upload to at least experimental? > > > > Sure, please raise a merge request against biboumi and I will try > > to > > review your work and sponsor the upload for you. I would be happy > > if > > you can join us in maintaining biboumi. Both me and Jonas are bit > > busy > > and not getting enough time for maintaining biboumi properly. > > You are following along on this bugreport, right? > > I think it would be helpful if you could give a rough estimate on > when > you expect to find time to review the package update. > > I don't mean to rush it, just suggest to be transparent about the > delay > - I can imagine that Alberto and Michel must be excited to see > progress > on their contributions. > > I must admit that I am a bit confused - seems we now have two > bugfixes > for this issue - first from Alberto and later from Michel who also > wants > to join as co-maintainer - hope you can resolve that, Vasudev :-) > > > - Jonas >
Bug#957037: biboumi: ftbfs with GCC-10
Quoting Vasudev Kamath (2020-12-15 09:35:35) > > Hi Alberto, > > > I have checked that current upstream (9.0) builds flawlessly, and > > made my release available at > > https://salsa.debian.org/aluaces-guest/biboumi . > > That is great. > > > Can I be sponsored so we can upload to at least experimental? > > Sure, please raise a merge request against biboumi and I will try to > review your work and sponsor the upload for you. I would be happy if > you can join us in maintaining biboumi. Both me and Jonas are bit busy > and not getting enough time for maintaining biboumi properly. You are following along on this bugreport, right? I think it would be helpful if you could give a rough estimate on when you expect to find time to review the package update. I don't mean to rush it, just suggest to be transparent about the delay - I can imagine that Alberto and Michel must be excited to see progress on their contributions. I must admit that I am a bit confused - seems we now have two bugfixes for this issue - first from Alberto and later from Michel who also wants to join as co-maintainer - hope you can resolve that, Vasudev :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#957037: biboumi: ftbfs with GCC-10
Hi Michel, Quoting Michel Le Bihan (2020-12-20 12:06:44) > I'm interested in joining the VoIP team to maintain this package long > term. I'm running it on my personal server and using it. I can't > become the only maintainer because I'm not a DM and all my uploads > will need to be sponsored. > > Sorry for the delay. It took me some time to understand how source of > this package is imported in the Salsa repo, but I think I did it > correctly now. https://salsa.debian.org/pkg-voip-team/biboumi > > I also contacted aluaces who also did some work on that update. That sounds great - all of it! And don't worry about being "slow" or making mistakes: We are all volunteers here and are happy to help guide you if needed. It is _normal_ to not know all details of Debian - don't expect that all is well documented but expect knowledge to require an ongoing collaboration and discussion. What I mean to say is that it is good that you try solve challenges on your own (e.g. the proper way to push code to Salsa), but feel free to ask if in doubt - and maybe even if you think you are *not* in doubt, because in many areas, there are more than one way to do things... To join the VoIP team, please subscribe to our mailinglist and request membership of our Gitlab group at Salsa - links to both are at https://wiki.debian.org/Teams/VoIP (since a moment ago - I did a much needed update of that wiki page just now). As for the concrete package update you made, please wait for Vasudev to have a look at it - I am quite busy with other tasks at the moment. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#957037: biboumi: ftbfs with GCC-10
Hello, I'm interested in joining the VoIP team to maintain this package long term. I'm running it on my personal server and using it. I can't become the only maintainer because I'm not a DM and all my uploads will need to be sponsored. Sorry for the delay. It took me some time to understand how source of this package is imported in the Salsa repo, but I think I did it correctly now. https://salsa.debian.org/pkg-voip-team/biboumi I also contacted aluaces who also did some work on that update. Michel Le Bihan
Bug#957037: biboumi: ftbfs with GCC-10
Hello, I updated the sources the same way you did and made a new release. Could you please check if everything is fine and sponsor my NMU? https://salsa.debian.org/mimi8/biboumi Michel Le Bihan On Thu, 17 Dec 2020 15:18:46 +0100 Jonas Smedegaard wrote: > Quoting Michel Le Bihan (2020-12-17 14:37:38) > > > @Michel: If you are interested in joining the VoIP team generally, > > > then please join the mailinglist and request membership to the Salsa > > > group - links are at https://wiki.debian.org/Teams/VoIP > > > > Sorry, but I'm not really interested in VoIP software nor have much > > experience with it. I'm interested in XMPP. Actually, I don't really > > understand why this package is managed by the VoIP team and not by the > > XMPP team. > > Sorry, I expressed that badly: What I meant to say is that if you care > for *this* package more generally (i.e. not only this once) then I > encourage you to join as package maintainer to help look after it. The > VoIP team provides infrastructure - you need not care for other packages > in the VoIP team. > > Reason Biboumi is maintained in the VoIP team is that Vasudev wanted my > help maintaining it, and I - just like you, if I understand correctly - > wanted to limit the amount of teams to attend to. I have an interest in > XMPP but am already involved with 20 other teams. > > I am open to having you and Vasudev move the package to the XMPP team, > but would hate to see the package become badly maintained: Vasudev has > not had a lot of time for packaging lately, and I don't know the level > of your devotion - that's why I suggest to start maintain it at its > current home where I can help keep an eye on it, and then maybe move it > later if you still prefer that after tending to it for some time. > > ...but if you are eager to help and joining the VoIP team is what holds > you back, then maybe it is best to simply hand over the package to you. > Please do share your thoughts on this. > > > Kind regards, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private
Bug#957037: biboumi: ftbfs with GCC-10
Hello, I noticed that https://salsa.debian.org/aluaces-guest/biboumi/-/commits/upstream doesn't have upstream imported the same way you have it. I think that I imported it correctly in https://salsa.debian.org/mimi8/biboumi/-/commits/upstream . However, I don't know how you generated the hash in `with Debian dir 49ca567d9a5a72a0874b26f332c3f441ca6783f5` in https://salsa.debian.org/mimi8/biboumi/-/commit/4efa9c854464d9087b673a0ef5ead39b92e6d109 . I would like to continue importing upstream releases the same way it was done before. Michel Le Bihan Le jeudi 17 décembre 2020 à 15:18 +0100, Jonas Smedegaard a écrit : > Quoting Michel Le Bihan (2020-12-17 14:37:38) > > > @Michel: If you are interested in joining the VoIP team > > > generally, > > > then please join the mailinglist and request membership to the > > > Salsa > > > group - links are at https://wiki.debian.org/Teams/VoIP > > > > Sorry, but I'm not really interested in VoIP software nor have much > > experience with it. I'm interested in XMPP. Actually, I don't > > really > > understand why this package is managed by the VoIP team and not by > > the > > XMPP team. > > Sorry, I expressed that badly: What I meant to say is that if you > care > for *this* package more generally (i.e. not only this once) then I > encourage you to join as package maintainer to help look after it. > The > VoIP team provides infrastructure - you need not care for other > packages > in the VoIP team. > > Reason Biboumi is maintained in the VoIP team is that Vasudev wanted > my > help maintaining it, and I - just like you, if I understand correctly > - > wanted to limit the amount of teams to attend to. I have an interest > in > XMPP but am already involved with 20 other teams. > > I am open to having you and Vasudev move the package to the XMPP > team, > but would hate to see the package become badly maintained: Vasudev > has > not had a lot of time for packaging lately, and I don't know the > level > of your devotion - that's why I suggest to start maintain it at its > current home where I can help keep an eye on it, and then maybe move > it > later if you still prefer that after tending to it for some time. > > ...but if you are eager to help and joining the VoIP team is what > holds > you back, then maybe it is best to simply hand over the package to > you. > Please do share your thoughts on this. > > > Kind regards, > > - Jonas >
Bug#957037: biboumi: ftbfs with GCC-10
Quoting Michel Le Bihan (2020-12-17 14:37:38) > > @Michel: If you are interested in joining the VoIP team generally, > > then please join the mailinglist and request membership to the Salsa > > group - links are at https://wiki.debian.org/Teams/VoIP > > Sorry, but I'm not really interested in VoIP software nor have much > experience with it. I'm interested in XMPP. Actually, I don't really > understand why this package is managed by the VoIP team and not by the > XMPP team. Sorry, I expressed that badly: What I meant to say is that if you care for *this* package more generally (i.e. not only this once) then I encourage you to join as package maintainer to help look after it. The VoIP team provides infrastructure - you need not care for other packages in the VoIP team. Reason Biboumi is maintained in the VoIP team is that Vasudev wanted my help maintaining it, and I - just like you, if I understand correctly - wanted to limit the amount of teams to attend to. I have an interest in XMPP but am already involved with 20 other teams. I am open to having you and Vasudev move the package to the XMPP team, but would hate to see the package become badly maintained: Vasudev has not had a lot of time for packaging lately, and I don't know the level of your devotion - that's why I suggest to start maintain it at its current home where I can help keep an eye on it, and then maybe move it later if you still prefer that after tending to it for some time. ...but if you are eager to help and joining the VoIP team is what holds you back, then maybe it is best to simply hand over the package to you. Please do share your thoughts on this. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#957037: biboumi: ftbfs with GCC-10
@Michel: If you are interested in joining the VoIP team generally, > then > please join the mailinglist and request membership to the Salsa group > - > links are at https://wiki.debian.org/Teams/VoIP Sorry, but I'm not really interested in VoIP software nor have much experience with it. I'm interested in XMPP. Actually, I don't really understand why this package is managed by the VoIP team and not by the XMPP team. Michel Le Bihan
Bug#957037: biboumi: ftbfs with GCC-10
Quoting Michel Le Bihan (2020-12-17 12:58:39) > It's not possible to open merge requests against > https://salsa.debian.org/pkg-voip-team/biboumi . They seem disabled for > that repo. That's probably true: I generally disable merge requests for git repos that I manage, because I am uncormfortable using those and don't want others to get a false impression that they will be processed. I am totally fine with others in the team managing MRs. @Michel: If you are interested in joining the VoIP team generally, then please join the mailinglist and request membership to the Salsa group - links are at https://wiki.debian.org/Teams/VoIP @Vasudev: If you are happy accepting merge requests, then feel free to enable them for this git repo. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#957037: biboumi: ftbfs with GCC-10
Hello, It's not possible to open merge requests against https://salsa.debian.org/pkg-voip-team/biboumi . They seem disabled for that repo. Michel Le Bihan
Bug#957037: biboumi: ftbfs with GCC-10
Hi Alberto, > I have checked that current upstream (9.0) builds flawlessly, and made > my release available at https://salsa.debian.org/aluaces-guest/biboumi > . That is great. > Can I be sponsored so we can upload to at least experimental? Sure, please raise a merge request against biboumi and I will try to review your work and sponsor the upload for you. I would be happy if you can join us in maintaining biboumi. Both me and Jonas are bit busy and not getting enough time for maintaining biboumi properly. Cheers, Vasudev
Bug#957037: biboumi: ftbfs with GCC-10
Package: biboumi Followup-For: Bug #957037 I have checked that current upstream (9.0) builds flawlessly, and made my release available at https://salsa.debian.org/aluaces-guest/biboumi . Can I be sponsored so we can upload to at least experimental? Thanks!
Bug#957037: biboumi: ftbfs with GCC-10
On Fri, 17 Apr 2020 10:57:04 + Matthias Klose wrote: > Package: src:biboumi > Version: 8.3-1 > Severity: normal > Tags: sid bullseye > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-10 > > Please keep this issue open in the bug tracker for the package it > was filed for. If a fix in another package is required, please > file a bug for the other package (or clone), and add a block in this > package. Please keep the issue open until the package can be built in > a follow-up test rebuild. > > The package fails to build in a test rebuild on at least amd64 with > gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The > severity of this report will be raised before the bullseye release, > so nothing has to be done for the buster release. > This issue was fixed in biboumi 8.5, see this commit in particular https://lab.louiz.org/louiz/biboumi/-/commit/fa905a741fca3bee255b32b09e9e63bd09270560 Also 8.4 fixes a potential crash that can be caused remotely, so it’s probably good to upgrade in stable, not just in unstable or testing. -- louiz’
