Bug#1028489: boost1.83 as default
Don't forget to raise the severity of the FTBFS bugreports to serious now that the new boost-defaults is in unstable. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1028489: boost1.83 as default
Hi Sebastian, uploded. Anton Am So., 17. Dez. 2023 um 18:13 Uhr schrieb Sebastian Ramacher : ... > Please go ahead. > > Cheers > -- > Sebastian Ramacher
Processed: Re: Bug#1028489: boost1.83 as default
Processing control commands: > tags -1 = confirmed Bug #1028489 [release.debian.org] transition: boost1.83 Added tag(s) confirmed; removed tag(s) trixie and moreinfo. -- 1028489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028489: boost1.83 as default
Control: tags -1 = confirmed Hi Anton On 2023-11-16 23:08:10 +0100, Anton Gladky wrote: > Hi Sebastian, > > bugs are filed: > > https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-boost183-transition=gl...@debian.org=1=1=1=1#results Please go ahead. Cheers -- Sebastian Ramacher
Bug#1054657: Transition ready? (Was: Transition seems to be blocked (Was: Bug#1054657: transition: r-bioc-biocgenerics))
Hi Andreas There are some packages that have still not migrated since the previous r-api-bioc-3.17 transition in July 2023. Links to their tracker pages, which should tell you what is needed, follow: https://tracker.debian.org/pkg/r-bioc-cner https://tracker.debian.org/pkg/r-bioc-dada2 https://tracker.debian.org/pkg/r-bioc-edaseq https://tracker.debian.org/pkg/r-bioc-ioniser https://tracker.debian.org/pkg/r-bioc-megadepth https://tracker.debian.org/pkg/r-bioc-scater https://tracker.debian.org/pkg/r-bioc-shortread https://tracker.debian.org/pkg/r-bioc-tcgabiolinks https://tracker.debian.org/pkg/r-bioc-tfbstools As a bonus, here's another, not related to the transition, but from a similar time: https://tracker.debian.org/pkg/r-cran-dials Regards Graham
[SUA 247-1] Updated linux packages
Hello, I'm encountering an issue with my 'Broadcom STA DKMS driver' when NetworkManager is active. Currently, I am awaiting the '[SUA 247-1] Updated linux packages' update, but I have not yet received it. Could you please assist me in resolving this issue? Thank you.
Re: Bug#1057755: Qt WebEngine Security Support In Stable
On Sat, Dec 16, 2023 at 04:33:58PM -0700, Soren Stoutner wrote: > On Saturday, December 16, 2023 4:10:42 PM MST Adrian Bunk wrote: > > On Sat, Dec 16, 2023 at 01:22:13PM -0700, Soren Stoutner wrote: > > > Bookworm released with qtwebengine-opensource-src 5.15.8+dfsg-1, but > > > 5.15.13+dfsg-1~deb12u1 was later uploaded. > > > > That's not true, bookworm released with 5.15.13+dfsg-1~deb12u1. > > How does stable initially release with an ~deb12u1? On Sat, Dec 16, 2023 at 06:00:28PM -0700, Soren Stoutner wrote: > Digging into this a little further, it looks like the current version of > Angelfish does not use > any Qt WebEngine private headers (qtwebengine5-private-dev is not listed as a > build- > depends). I don't know what's going on with the headers, but there is a reason why the dependency gets generated: $ nm -D /usr/bin/angelfish-webapp | grep Qt_5_PRIVATE_API U _ZN22QQuickWebEngineProfile16downloadFinishedEP27QQuickWebEngineDownloadItem@Qt_5_PRIVATE_API U _ZN22QQuickWebEngineProfile17downloadRequestedEP27QQuickWebEngineDownloadItem@Qt_5_PRIVATE_API $ You are jumping to conclusions too fast without double-checking things, which is not a good sign for someone who wants to provide security support for what is perhaps the most difficult to support package in Debian. That's also true for the whole effort: Everyone who has looked at this before came to the conclusion that security support for browser engines is no longer possible on a volunteer basis in Debian since it is: - a lot of work for many CVEs, and - requires deep technical skills of the browser engine (How much experience do you have modifying the Blink code?), and - backporting fixes to ancient versions of software is sometimes easy but sometimes the kind of nasty work most people won't do unpaid It is not fundamentally impossible, but it's in the order of magnitude of one full-time employed Blink engineer. >... > Now that is all cleared up, I think that next week I am going to build the > current version > of Qt 5 WebEngine for stable and test it on a system I have running locally, > focusing > specifically on all of the browsers that use Qt WebEngine. If all seems to > work well, would > anyone have any objections to me uploading it to bookworm-backports? >... bookworm-backports are packages from trixie rebuilt for bookworm. Whatever you want to do in backports, it has to go into unstable und migrate to testing first. cu Adrian
Bug#1054657: marked as done (transition: r-bioc-biocgenerics)
Your message dated Sun, 17 Dec 2023 10:19:26 +0100 with message-id <3bcff6da-fe14-40e7-bf90-0d476ff1f...@debian.org> and subject line Re: Bug#1054657: Transition ready? (Was: Transition seems to be blocked (Was: Bug#1054657: transition: r-bioc-biocgenerics)) has caused the Debian Bug report #1054657, regarding transition: r-bioc-biocgenerics to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1054657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition X-Debbugs-Cc: r-bioc-biocgener...@packages.debian.org, debia...@lists.debian.org Control: affects -1 + src:r-bioc-biocgenerics Hi, BioConductor has just released version 3.17. Since the next r-base release is pending on 2023-10-31 we do not think it is a good idea to start the transition before but it might make sense to open this bug right now. (No idea whether we will see a proper r-api transition but building everything against the new r-base sounds like less hassle than doing r-api-bioc transition right now.) The BioConductor transition will bump the virtual package r-api-bioc-3.17 to r-api-bioc-3.18. BTW, I'm aware that a couple of r-bioc-* packages did not yet migrated to testing due to some autopkgtest issues on some architectures. We decided that it makes sense to do the transition first and approach upstream about their latest release in case those issues might remain. Kind regards and thanks a lot for your work as release team Andreas. Ben file: title = "r-bioc-biocgenerics"; is_affected = .depends ~ "r-api-bioc-3.17" | .depends ~ "r-api-bioc-3.18"; is_good = .depends ~ "r-api-bioc-3.18"; is_bad = .depends ~ "r-api-bioc-3.17"; --- End Message --- --- Begin Message --- Hi, On 14-12-2023 08:58, Andreas Tille wrote: Please let me know when I (realistically) can do more than just that source-only upload mentioned above. Waiting seems to have been enough. I pulled some strings on the back side and the whole set migrated yesterday. Paul OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message ---
