Bug#1004445: Removed package(s) from unstable
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: clazy | 1.10-2 | i386 clazy-tests | 1.10-2 | i386 --- Reason --- RoQA; no longer builds on i386 -- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1004...@bugs.debian.org. The full log for this bug can be viewed at https://bugs.debian.org/1004445 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)
Processed: unblock 1000941 with 1000934
Processing commands for cont...@bugs.debian.org: > unblock 1000941 with 1000934 Bug #1000941 [ftp.debian.org] RM: llvm-toolchain-11 -- ROM; Limit the number of llvm versions 1000941 was blocked by: 1000934 1000925 1000933 1000909 1000937 1000919 1000911 1000929 1000918 1000930 1000932 1000915 1000936 1000931 1000938 1000927 1001317 1000923 1000910 1000924 1000912 1000916 1000935 1000914 1000920 1000922 1000926 1000913 1000917 1000939 1000941 was not blocking any bugs. Removed blocking bug(s) of 1000941: 1000934 > thanks Stopping processing here. Please contact me if you need assistance. -- 1000941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1000934 is important
Processing commands for cont...@bugs.debian.org: > severity 1000934 important Bug #1000934 [src:clazy] clazy: FTBFS on i386 with llvm-toolchain-13 Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: The future of KDE in Debian?
Allan Sandfeld Jensen - 28.01.22, 16:24:07 CET: > On Montag, 24. Januar 2022 21:20:11 CET Marco Valli wrote: > > O-h m-y g-o-d... > > > > https://www.phoronix.com/scan.php?page=news_item=Qt-Digital-Adver > > tising-1 .0 > > > > Regards > > Maybe I am missing something, what is the problem with a company > releasing a new product for paying customers. A new product that has > nothing to with Debian, KDE or what we use of Qt? > > I mean it will likely make the products of those paying customers > objectively worse, but we can just choose not to use those products, > which aren't Open Source anyway. No, you are not missing anything here. There is nothing to see here. Even if you do not agree with this move by The Qt Company. As long as KDE developers stay their current course, there is nothing to worry about. Best, -- Martin
Re: The future of KDE in Debian?
On Montag, 24. Januar 2022 21:20:11 CET Marco Valli wrote: > O-h m-y g-o-d... > > https://www.phoronix.com/scan.php?page=news_item=Qt-Digital-Advertising-1 > .0 > > Regards Maybe I am missing something, what is the problem with a company releasing a new product for paying customers. A new product that has nothing to with Debian, KDE or what we use of Qt? I mean it will likely make the products of those paying customers objectively worse, but we can just choose not to use those products, which aren't Open Source anyway. Allan
