Bug#1066077: usr-is-merged fails to install on a /usr-merged system
Yeah, I moved /usr quite a while ago. IIRC things went sideways halfway through and I ended up needing to manually run mv with ld-linux.so and LD_LIBRARY_PATH, but it got fixed eventually. On Sun, Aug 25, 2024, 15:45 Marco d'Itri wrote: > Control: tag -1 wontfix > > On Mar 12, David W wrote: > > > In the end, it turned out to be because /usr itself was a symlink, and > > although this causes no issues for either the merging process or any > > running software, since the check is using "readlink -f" it erroneously > > fails. > I understand the issue, but right now I cannot see a simple way to > make the check work with your setup. > Development of usrmerge started 10 years ago and the program will be > retired with the next Debian release: at this point I do not feel like > introducing major changes anymore for marginal use cases. > > You can easily rename /usr by installing busybox-static and then running > "busybox ash": you will get a shell which magically uses all the > busybox built-in commands. > > -- > ciao, > Marco >
Bug#1064726: 0ad: FTBFS: ImportError: cannot import name 'dist' from 'distutils' (/usr/lib/python3.11/distutils/__init__.py)
Hi, I found that adding Build-Depends: python3-distutils solves this problem. The natural question is why did build of 0ad work in the past, but not now. I found that python3-distutils was being pulled in only as a side effect of one of the dependencies, libsdl2-dev. The build failure is caused by the fact that the Debian package of glib2.0 stopped depending on python3-distutils as of 23 Jan 2024. Specifically, libsdl2-dev depends on libibus-1.0-dev, which depends on libglib2.0-dev, which depends on libglib2.0-dev-bin, which used to depend on python3-distutils, but now depends on python3-packaging. This change was made to libglib2.0-dev-bin in version 2.78.3-2 on 23 Jan 2024. I've committed the Build-Depends change to Debian Salsa. Thanks. -- David W. Kennedy
Bug#1066077: usr-is-merged fails to install on a /usr-merged system
On Tue, Mar 12, 2024, 06:04 Luca Boccassi wrote: > Why is /usr a symlink? How did you install your debian system? > It's something I set up manually 15 years ago or something, to deal with a situation where /usr plus some other static directories needed to live on a different hard drive. Different times... Obviously not something any installer will ever do, but I don't think it's against policy? Given that packages depend on usr-is-merged to signal proper merged state, it shouldn't force you to undo that (especially given that it's a very risky/tricky operation). >
Bug#1066077: usr-is-merged fails to install on a /usr-merged system
Package: usr-is-merged Version: 39 When attempting to install, I received the following message: ** * * The usr-is-merged package cannot be installed because this system does * not have a merged /usr. * * Please install the usrmerge package to convert this system to merged-/usr. * * For more information please read https://wiki.debian.org/UsrMerge. * ** This despite the fact that I have version 39 of usrmerge installed, and the symlinks were indeed set up correctly. In the end, it turned out to be because /usr itself was a symlink, and although this causes no issues for either the merging process or any running software, since the check is using "readlink -f" it erroneously fails. -- =D ave
Bug#1033365: 0ad: Build fails if python3-setuptools is installed
Package: 0ad Version: 0.0.26-3 Severity: normal If the user has python3-setuptools, version 58.3.0 or higher, installed in a Debian sid build environment when building 0ad then build fails. To confirm that python3-setuptools is a minimal case for reproduction of symptoms, I also tested build of 0ad without python3-setuptools, but with each of the dependency packages of python3-setuptools. In that case build was successful. I have also tested with python3-setuptools versions 58.2.0-1 and 52.0.0-4, and build of 0ad was successful with those versions. I used matching versions of python3-pkg-resources for the tests. I think that the cause of the failure to build 0ad with python3-setuptools version >= 58.3.0 is that easyinstall was deprecated in python3-setuptools on 2021-10-22. Version 58.3.0 is the next upstream release after that. Steps to reproduce: # sbuild-createchroot sid /path/to/chroot/sid [debian mirror] # cd / # schroot -c source:sid-amd64-sbuild # mkdir /home/myusername (replace "myusername" with your primary username outside the chroot) # cp -r /etc/skel/. /home/myusername # chown -R myusername:myusername /home/myusername # chmod g+ws /home/myusername # chmod o-rx /home/myusername # apt-get update # apt-get install --no-install-recommends python3-setuptools (installs several packages, but the only packages that would not otherwise be installed by `apt-get build-dep 0ad` are: python3-pkg-resources python3-setuptools) # dpkg --status python3-setuptools | grep '^Version' (output is Version: 66.1.1-1) # dpkg --status python3-pkg-resources | grep '^Version' (output is Version: 66.1.1-1) # exit $ sbuild -d sid-amd64-sbuild 0ad_0.0.26-3 Excerpt of output from steps to reproduce: patching file python/mozbuild/mozbuild/preprocessor.py patching file python/mozbuild/mozbuild/util.py Creating Python 3 environment /usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( created virtual environment CPython3.11.2.final.0-64 in 239ms creator CPython3Posix(dest=/<>/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/_virtualenvs/init_py3, clear=False, global=False) seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/tmp/tmppfskju67) added seed packages: pip==20.2.2, setuptools==49.6.0, wheel==0.35.1 activators BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator [...] Job: 0ad_0.0.26-3 Machine Architecture: amd64 Package: 0ad Source-Version: 0.0.26-3 Status: attempted Version: 0.0.26-3 E: Build failure (dpkg-buildpackage died) Solutions: Option 1. We look for a root cause and fix the bug that causes build failure if the user happens to have python3-setuptools installed. An idea would be to configure the virtualenv to use the builtin version of python3-setuptools. Option 2. Alternatively, we add "Build-Conflicts: python3-setuptools (>= 58.3.0)" to the control file of the Debian package of 0ad. I'll send the latter fix, probably via Salsa.
Bug#1033175: FTBFS: setup.py install is deprecated
Package: 0ad Version: 0.0.26-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: dav...@reasoned.us Hello, When I try to build 0ad version 0.0.26-3 in Debian unstable with python3.11 and python3-virtualenv, build fails. I think that the key error message is "/usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools." The commands that I use to build the package: # apt-get update # apt-get build-dep 0ad $ apt-get source 0ad $ cd 0ad-0.0.26 $ debuild Here is an excerpt of the output. [...] patching file python/mozbuild/mozbuild/preprocessor.py patching file python/mozbuild/mozbuild/util.py Creating Python 3 environment /usr/lib/python3/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools. warnings.warn( created virtual environment CPython3.11.2.final.0-64 in 139ms creator CPython3Posix(dest=/home/myusername/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/_virtualenvs/init_py3, clear=False, global=False) seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/myusername/.local/share/virtualenv) added seed packages: pip==20.2.2, setuptools==49.6.0, wheel==0.35.1 activators BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator,XonshActivator Traceback (most recent call last): File "/home/myusername/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/../js/src/../../configure.py", line 181, in sys.exit(main(sys.argv)) ^^ File "/home/myusername/0ad-0.0.26/libraries/source/spidermonkey/mozjs-78.6.0/build-debug/../js/src/../../configure.py", line 52, in main sandbox.run(os.path.join(os.path.dirname(__file__), 'moz.configure')) [...]
Bug#1020649: New minisign public key for 0ad
Via email from Stan: upstream changed their minisign public key for verifying the integrity of alpha 0.0.26 and beyond. Stan said that he is the controller of the minisign key for 0 A.D. Instructions, and the updated minisign public key, are at the following website. https://trac.wildfiregames.com/wiki/VerifyingYourDownloads -- Dave Kennedy
Bug#1020649: 0ad: New upstream release - version 0.0.26
Package: 0ad Version: 0.0.25b-2+b2 Severity: wishlist Dear Maintainer, Version 0.0.26 of 0ad was just released. New Features in version 0.0.26. * A new civilization: The Han. * New campaign maps: Tarim basin and Yangtze. * Now units have acceleration. * Twenty-six new music tracks. * New and updated art. * Bug fixes for newer hardware * More improvements. Source is available at https://play0ad.com/download/source/ Build instructions are available at https://trac.wildfiregames.com/wiki/BuildInstructions -- Dave Kennedy
Bug#992170: How to test a stable package in sid
Hello Robbi, It is possible to test a stable package in Debian sid. You can create a minimal debootstrap of the stable distribution, then chroot to it and install the 0ad-data/bullseye package. Here are example commands for this. I don't think that it is strictly required that you do this in order to close the bug report, but if you want to be extra thorough then you can do this before closing the report. There is a remote possibility that there is a bug in 0ad-data triggered by obscure hardware. Commands preceded by a # indicate that you should run them as root or with sudo. # apt-get install debootstrap # mkdir /bullseye # debootstrap bullseye /bullseye https://deb.debian.org/debian # chroot /bullseye # apt-get update Note that if networking isn't working in the chroot then you likely need to configure the DNS resolver, such as in /etc/resolv.conf. # apt-get upgrade # apt-get install 0ad-data/bullseye 0ad-data-common/bullseye 0ad/bullseye When it finishes, you can exit the chroot by typing exit or pressing Ctrl-D. # exit -- Dave Kennedy
Bug#992170: Thanks for the follow-up
Hello Robbi, Thanks for the follow-up. It helps with package maintenance to have confirmation about this. I agree that we can conclude that it's not a bug in 0ad. I have noticed a correlation between faulty power supplies and faulty hard drives. So you might want to check or preemptively replace your power supply. This advice assumes that there wasn't excessive physical force on your hard drive, such as moving the computer while the hard drive was spinning or a collision of some sort. You can close this bug following the steps in link [1]. Ignore the statements about the requirement of a new version of the package in order to close a bug, because that requirement is not applicable in this case. Basically, send email to 992170-d...@bugs.debian.org and in the body of the email include a brief statement that you had a hardware problem and the symptoms are unreproducible since you have replaced the hard drive (assuming that is actually true). If it doesn't make sense then nevermind, and the package maintainer will later close this bug. Thanks. Links [1] https://www.debian.org/Bugs/Developer#closing -- Dave Kennedy
Bug#992170: Works for me
Works for me. Logs demonstrating download, extraction and examination of the current bullseye version of 0ad-data are attached. Here is an excerpt. $ ls -l /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb -rw-r--r-- 1 root root 701833824 Jan 1 2021 /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb $ md5sum /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb b2b6e5510898abf0eee79da48995f92f /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb $ apt-cache show 0ad-data/bullseye | grep MD5sum MD5sum: b2b6e5510898abf0eee79da48995f92f According to your first message, the MD5sum of your copy is "2688ba115bc50916975827a9f57052bd". There is an MD5 mismatch on the copy of 0ad-data_0.0.23.1-1.1_all.deb that you have obtained. This can be caused by hardware or software malfunction or incompatibility on your computer. It could also be caused by data corruption or tampering on the mirror from which you obtained the file. Try downloading the file from a different Debian mirror. Also test downloading and installing 0ad-data version 0.0.23 on a different computer. Please check the system that has the MD5sum mismatch for bad RAM (run memtest86+), a failing hard drive (use smartmontools/smartctl) or other hardware problems. I once had a problem with single-bit errors in files stored on an old computer. I later discovered that the there were distended (bulging and failed) capacitors in the power supply and motherboard. If you want to know what failing capacitors look like, go to https://badcaps.net/ and click "How to Identify" at the left. Note that capacitors might fail without visible signs. Another time that I observed apparent data corruption was during testing of new RAM. Kernel compilation failed intermittently with segfaults. This turned out to be caused by a bug in the Linux kernel. Thanks.root@five-o:~# apt-get install --download-only 0ad-data/bullseye Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '0.0.23.1-1.1' (Debian:11.0/stable [all]) for '0ad-data' Suggested packages: 0ad The following NEW packages will be installed: 0ad-data 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 702 MB of archives. After this operation, 2,093 MB of additional disk space will be used. Get:1 https://mirrors.wikimedia.org/debian bullseye/main amd64 0ad-data all 0.0.23.1-1.1 [702 MB] Fetched 621 MB in 1min 29s (7,006 kB/s) Download complete and in download only mode $ dpkg-deb --raw-extract ./0ad-data_0.0.23.1-1.1_all.deb /tmp/0ad-data-0.0.23 $ cd /tmp/0ad-data-0.0.23/ $ ls DEBIAN usr $ find . ./DEBIAN ./DEBIAN/md5sums ./DEBIAN/control ./usr ./usr/share ./usr/share/doc ./usr/share/doc/0ad-data ./usr/share/doc/0ad-data/changelog.Debian.gz ./usr/share/doc/0ad-data/copyright ./usr/share/games ./usr/share/games/0ad ./usr/share/games/0ad/mods ./usr/share/games/0ad/mods/mod ./usr/share/games/0ad/mods/mod/mod.zip ./usr/share/games/0ad/mods/public ./usr/share/games/0ad/mods/public/public.zip $ ls -l usr/share/games/0ad/mods/public/public.zip -rw-r--r-- 1 dave dave 2057825096 Jan 1 2021 usr/share/games/0ad/mods/public/public.zip $ ls -l /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb -rw-r--r-- 1 root root 701833824 Jan 1 2021 /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb $ md5sum /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb b2b6e5510898abf0eee79da48995f92f /var/cache/apt/archives/0ad-data_0.0.23.1-1.1_all.deb $ apt-cache show 0ad-data/bullseye | grep -i md5sum MD5sum: b2b6e5510898abf0eee79da48995f92f
Bug#992314: Add found version and add patch tag
Control: found -1 0.0.23.1-5+b1 Control: tags -1 + patch thanks
Bug#992017: Updated patch and example script for building the package
Hello, Here is an updated patch and rationale for depencency versions with some improvements. I have tested building and running this in a Debian stable (bullseye) chroot and a Debian unstable (sid) chroot. About 12 GiB of disk space is needed for building, and an additional 20 GiB for an OS with necessary packages for building 0ad. Building with an SSD and a quad core desktop CPU requires about 30 minutes. I have also provided a bash script that shows how to obtain the necessary source code, apply the patch and build the Debian package of 0ad version 0.0.25. You should really start with building and installing version 0.0.25 of 0ad-data, for which a patch and instructions are available in bug #992314. Notes about the process of building the Debian package for 0ad, version 0.0.25, follow. If you are asked for a default mirror for pbuilder then the most common response is: https://deb.debian.org/debian but a list of local mirrors is available here https://www.debian.org/mirror/list I recommend using a mirror that supports HTTPS encryption. You will need to manually test which mirrors support HTTPS, for example with a web browser. Thanks -- Dave Kennedydiff -ur 0ad-0.0.24b-2/debian/changelog 0ad-0.0.25/debian/changelog --- 0ad-0.0.24b-2/debian/changelog 2021-08-15 17:50:57.379685891 -0500 +++ 0ad-0.0.25/debian/changelog 2021-08-16 12:17:49.089508040 -0500 @@ -1,3 +1,16 @@ +0ad (0.0.25-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * New upstream release. + * d/control: Update required versions of dependencies. + * d/rules: Clean up build files for libnvtt and spidermonkey in +dh_auto_clean. + * d/rules: Exclude libmozjs78-ps-release.so from dh_dwz in order to work +around a crash in dwz. + * d/watch: Update URL for releases. + + -- David W. Kennedy Sun, 15 Aug 2021 15:07:54 -0500 + 0ad (0.0.24b-2) UNRELEASED; urgency=medium [ Pino Toscano ] diff -ur 0ad-0.0.24b-2/debian/control 0ad-0.0.25/debian/control --- 0ad-0.0.24b-2/debian/control 2021-08-15 17:50:57.379685891 -0500 +++ 0ad-0.0.25/debian/control 2021-08-16 12:40:19.474742410 -0500 @@ -7,32 +7,35 @@ Ludovic Rousseau Build-Depends: autoconf, + automake, cargo, cmake, debhelper-compat (= 12), dpkg-dev (>= 1.15.5), - libboost-dev, - libboost-filesystem-dev, - libcurl4-gnutls-dev | libcurl4-dev, + libboost-dev (>= 1.57.0.1), + libboost-filesystem-dev (>= 1.57.0.1), + libcurl4-gnutls-dev (>= 7.32.0) | libcurl4-dev (>= 7.32.0), libenet-dev (>= 1.3), - libfmt-dev, + libfmt-dev (>= 4.0.0), libgloox-dev (>= 1.0.10), - libicu-dev, + libicu-dev (>= 67.1-4~), libminiupnpc-dev (>= 1.6), libnspr4-dev, libogg-dev, libopenal-dev, libpng-dev, - libsdl2-dev (>= 2.0.2), + libsdl2-dev (>= 2.0.5), libsodium-dev (>= 1.0.14), libvorbis-dev, libwxgtk3.0-gtk3-dev, libxcursor-dev, libxml2-dev, + llvm, pkg-config, python3, - rustc, - zlib1g-dev + rustc (>= 1.41), + tzdata, + zlib1g-dev (>= 1:1.2.3) Standards-Version: 4.5.0 Homepage: http://play0ad.com/ Vcs-Git: https://salsa.debian.org/games-team/0ad.git diff -ur 0ad-0.0.24b-2/debian/rules 0ad-0.0.25/debian/rules --- 0ad-0.0.24b-2/debian/rules 2021-08-15 17:50:57.379685891 -0500 +++ 0ad-0.0.25/debian/rules 2021-08-16 12:19:35.940339723 -0500 @@ -24,10 +24,12 @@ find binaries/system/ -type f ! -name readme.txt -delete rm -f libraries/fcollada/lib/*.a rm -f build/premake/.*.tmp - rm -f libraries/source/spidermonkey/lib/* + rm -rf libraries/source/spidermonkey/lib rm -f libraries/source/cxxtest-4.4/python/cxxtest/*.pyc rm -f libraries/source/fcollada/lib/* rm -rf libraries/source/spidermonkey/include-unix-* + rm -rf libraries/source/spidermonkey/mozjs-78.6.0 + rm -f libraries/source/nvtt/lib/*.so rm -f source/ps/tests/stub_impl_hack.cpp dh_auto_clean @@ -59,3 +61,6 @@ override_dh_makeshlibs: dh_makeshlibs -Xusr/lib/games/0ad + +override_dh_dwz: + dh_dwz -Xlibmozjs78-ps-release.so diff -ur 0ad-0.0.24b-2/debian/watch 0ad-0.0.25/debian/watch --- 0ad-0.0.24b-2/debian/watch 2021-08-15 17:50:57.379685891 -0500 +++ 0ad-0.0.25/debian/watch 2021-08-15 17:50:57.647682959 -0500 @@ -1,2 +1,2 @@ version=3 -http://sf.net/zero-ad/0ad-([\d\.]+)-.*-unix-build\.tar\.xz +https://releases.wildfiregames.com/0ad-([\d\.]+)-.*-unix-build\.tar\.gz #!/bin/sh echo "This script assumes that you have already installed" echo "0ad-data_0.0.25-1.1_all.deb and 0ad-data-common_0.0.25-1.1_all.deb" echo "and run the following commands as root:" echo " apt-get update" echo " apt-get install build-essential pbuilder wget locales" echo " dpkg-reconfigure locales" echo " # On Debian bullseye (current stable) or sid (unstable), run the following" echo " # additional commands as root in order to install the build dependencies that" echo " # are specific to 0ad version 0.0.25:" echo " apt-get
Bug#992314: New upstream release of 0ad-data - version 0.0.25
Package: 0ad-data Version: 0.0.24b-1 Severity: wishlist Dear Maintainer, Version 0.0.25 of 0ad-data was released. I have attached a patch relative to version 0.0.24b-1. When combined with the upstream source for 0ad-data 0.0.25, it allows one to build a Debian package of 0ad-data version 0.0.25. The attached script shows the commands and/or helps automate the process of testing this patch. Thanks. -- Dave Kennedydiff -ur 0ad-data-0.0.24b-1/debian/changelog 0ad-data-0.0.25-1.1/debian/changelog --- 0ad-data-0.0.24b-1/debian/changelog 2021-03-07 03:27:19.0 -0600 +++ 0ad-data-0.0.25-1.1/debian/changelog 2021-08-16 15:01:02.774419655 -0500 @@ -1,3 +1,10 @@ +0ad-data (0.0.25-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * New upstream release. + + -- David W. Kennedy Mon, 16 Aug 2021 15:00:09 -0500 + 0ad-data (0.0.24b-1) experimental; urgency=medium * New upstream release. #!/bin/sh echo "This script assumes that you have already run the following commands as root:" echo " apt-get update" echo " apt-get install build-essential pbuilder wget locales fonts-freefont-ttf fonts-texgyre fonts-dejavu-core" echo " dpkg-reconfigure locales" #echo " # On Debian bullseye (current stable) or sid (unstable), run the following" #echo " # additional commands as root in order to install the build dependencies that" #echo " # are specific to 0ad version 0.0.25:" #echo " apt-get install cargo cmake libboost-dev libboost-filesystem-dev libcurl4-gnutls-dev libenet-dev libfmt-dev libgloox-dev libicu-dev libminiupnpc-dev libnspr4-dev libogg-dev libopenal-dev libpng-dev libreadline-dev libsdl2-dev libsdl2-dev libsodium-dev libvorbis-dev libwxgtk3.0-gtk3-dev libxcursor-dev libxml2-dev llvm pkg-config rustc zlib1g-dev" echo "" if [ \! -r 0ad-data-0.0.24b-1_to_0ad-data-0.0.25-1.1.diff ] ; then echo "Please ensure that 0ad-data-0.0.24b-1_to_0ad-data-0.0.25-1.1.diff is in the current working directory." exit fi mkdir -p 0ad-data-0.0.25-1.1_build cd 0ad-data-0.0.25-1.1_build wget https://releases.wildfiregames.com/0ad-0.0.25-alpha-unix-data.tar.xz mv 0ad-0.0.25-alpha-unix-data.tar.xz 0ad-data_0.0.25.orig.tar.xz mkdir 0ad-data-0.0.25 if [ $? -ne 0 ] ; then echo "Directory 0ad-data-0.0.25 already exists. Remove and try again?" exit fi echo "Extracting the 0ad-data upstream tarball. This may take several minutes." tar --strip-components 1 -Jxkf 0ad-data_0.0.25.orig.tar.xz -C 0ad-data-0.0.25 echo "Done extracting." wget https://deb.debian.org/debian/pool/main/0/0ad-data/0ad-data_0.0.24b-1.debian.tar.xz mkdir 0ad-data-0.0.24b-1 tar -Jxkf 0ad-data_0.0.24b-1.debian.tar.xz -C 0ad-data-0.0.24b-1 cp -a 0ad-data-0.0.24b-1/debian 0ad-data-0.0.25 cd 0ad-data-0.0.25 patch -p1 < ../../0ad-data-0.0.24b-1_to_0ad-data-0.0.25-1.1.diff tar -Jcf ../0ad-data_0.0.25-1.1.debian.tar.xz debian echo "" echo "Now run the following commands:" echo " cd 0ad-data-0.0.25-1.1_build/0ad-data-0.0.25" echo " dpkg-checkbuilddeps" echo " # (install any remaining unmet build dependencies as root)" echo " # then run the following commands:" echo " debuild" echo " cd .." echo " # then run this command as root" echo " apt install ./0ad-data_0.0.25-1.1_all.deb ./0ad-data-common_0.0.25-1.1_all.deb"
Bug#992135: Add found version
Control: found -1 0.0.24b-1 Thanks
Bug#992135: Manpage is missing documentation of many command line arguments
Package: 0ad Version: 0.0.23.1-5+b1 Severity: wishlist Hello, Many command line arguments are undocumented in the Debian manpage for 0ad. Most or all of them are documented in the 0ad README.txt file, so it could help speed up the process of updating the manpage. The README.txt is available at https://github.com/0ad/0ad/blob/master/binaries/system/readme.txt Based on searching the source code for "Args", I found these switches that are not documented in the manpage. This list is not exhaustive. in source/main.cpp: --rl-interface --autostart-nonvisual --unique-logs --replay-visual [arguments] (apparently paths of mods to install) --serializationtest --rejointest --ooslog --hashtest-full --hashtest-quick command line arguments to Atlas, the map editor, are in ps/GameSetup/Atlas.cpp in ps/GameSetup/GameSetup.cpp: --autostart-seed (or is this just an internal name for autostart-random=SEED?) --autostart-disable-replay --autostart-aiseed --autostart-team --autostart-ceasefire --autostart-aidiff --autostart-civ --autostart-victory --autostart-wonderduration --autostart-relicduration --autostart-reliccount --autostart-player (is this equivalent to autostart-players? Maybe substring matching is done on command line switches? autostart-players is already documented in the Debian manpage) -- Dave Kennedy
Bug#992017: Patch and info
Control: tags -1 + patch I have attached a patch relative to the 0ad Debian package version 0.0.24b-2 (on the Debian salsa repository) that allows building a binary package of 0.0.25 with the default debuild(1) process. I hereby release my modifcations under the Creative Commons CC0 license, which is public domain. Let me know if you prefer a different license. Using debuild has exposed a bug with either dwz or the bundled mozjs library. dwz crashes with an assert (relevant build logs attached as "dh_dwz crash when processing libmozjs78-ps-release.so.txt"). I worked around the crash with an override to dh_dwz in d/rules. An alternative solution might be to apply patches from the Debian package mozjs-78-0. I have also attached a file that explains why each version was chosen for each updated dependency line in the control file. The file name is "dependency version rationale.txt". Thanks diff -ur 0ad-0.0.24b-2_debian_salsa_version/debian/changelog 0ad-0.0.25-1+nmu1/debian/changelog --- 0ad-0.0.24b-2_debian_salsa_version/debian/changelog 2021-08-09 21:29:53.0 -0500 +++ 0ad-0.0.25-1+nmu1/debian/changelog 2021-08-12 16:38:03.0 -0500 @@ -1,3 +1,16 @@ +0ad (0.0.25-1+nmu1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * New upstream release. + * d/control: Update required versions of dependencies. + * d/rules: Clean up build files for libnvtt and spidermonkey in +dh_auto_clean. + * d/rules: Exclude libmozjs78-ps-release.so from dh_dwz in order to work +around a crash in dwz. + * d/watch: Update URL for releases. + + -- David W. Kennedy Mon, 09 Aug 2021 22:32:21 + + 0ad (0.0.24b-2) UNRELEASED; urgency=medium [ Pino Toscano ] diff -ur 0ad-0.0.24b-2_debian_salsa_version/debian/control 0ad-0.0.25-1+nmu1/debian/control --- 0ad-0.0.24b-2_debian_salsa_version/debian/control 2021-08-09 21:29:53.0 -0500 +++ 0ad-0.0.25-1+nmu1/debian/control 2021-08-12 17:07:01.0 -0500 @@ -11,13 +11,13 @@ cmake, debhelper-compat (= 12), dpkg-dev (>= 1.15.5), - libboost-dev, - libboost-filesystem-dev, - libcurl4-gnutls-dev | libcurl4-dev, + libboost-dev (>= 1.57.0.1), + libboost-filesystem-dev (>= 1.57.0.1), + libcurl4-gnutls-dev (>= 7.32.0) | libcurl4-dev (>= 7.32.0), libenet-dev (>= 1.3), - libfmt-dev, + libfmt-dev (>= 4.0.0), libgloox-dev (>= 1.0.10), - libicu-dev, + libicu-dev (>= 67.1-4~), libminiupnpc-dev (>= 1.6), libnspr4-dev, libogg-dev, @@ -29,10 +29,11 @@ libwxgtk3.0-gtk3-dev, libxcursor-dev, libxml2-dev, + llvm, pkg-config, python3, - rustc, - zlib1g-dev + rustc (>= 1.41), + zlib1g-dev (>= 1:1.2.3) Standards-Version: 4.5.0 Homepage: http://play0ad.com/ Vcs-Git: https://salsa.debian.org/games-team/0ad.git diff -ur 0ad-0.0.24b-2_debian_salsa_version/debian/rules 0ad-0.0.25-1+nmu1/debian/rules --- 0ad-0.0.24b-2_debian_salsa_version/debian/rules 2021-08-09 21:29:53.0 -0500 +++ 0ad-0.0.25-1+nmu1/debian/rules 2021-08-12 17:16:25.0 -0500 @@ -24,10 +24,12 @@ find binaries/system/ -type f ! -name readme.txt -delete rm -f libraries/fcollada/lib/*.a rm -f build/premake/.*.tmp - rm -f libraries/source/spidermonkey/lib/* + rm -rf libraries/source/spidermonkey/lib rm -f libraries/source/cxxtest-4.4/python/cxxtest/*.pyc rm -f libraries/source/fcollada/lib/* rm -rf libraries/source/spidermonkey/include-unix-* + rm -rf libraries/source/spidermonkey/mozjs-78.6.0 + rm -f libraries/source/nvtt/lib/*.so rm -f source/ps/tests/stub_impl_hack.cpp dh_auto_clean @@ -57,5 +59,8 @@ override_dh_strip: dh_strip --dbgsym-migration='0ad-dbg (<< 0.0.20-2~)' +override_dh_dwz: + dh_dwz -Xlibmozjs78-ps-release.so + override_dh_makeshlibs: dh_makeshlibs -Xusr/lib/games/0ad diff -ur 0ad-0.0.24b-2_debian_salsa_version/debian/watch 0ad-0.0.25-1+nmu1/debian/watch --- 0ad-0.0.24b-2_debian_salsa_version/debian/watch 2021-08-09 21:29:53.0 -0500 +++ 0ad-0.0.25-1+nmu1/debian/watch 2021-08-12 16:43:56.0 -0500 @@ -1,2 +1,2 @@ version=3 -http://sf.net/zero-ad/0ad-([\d\.]+)-.*-unix-build\.tar\.xz +https://releases.wildfiregames.com/0ad-([\d\.]+)-.*-unix-build\.tar\.gz [snip] dh_dwz dwz: debian/0ad/usr/lib/games/0ad/libmozjs78-ps-release.so: Couldn't find DIE at [743e7f3] referenced by DW_AT_abstract_origin from DIE at [743e8eb] dwz: debian/0ad/usr/games/pyrogenesis: DWARF compression not beneficial - old size 133599705 new size 134674971 dwz: debian/0ad/usr/lib/games/0ad/libAtlasUI.so: DWARF compression not beneficial - old size 21795508 new size 21842246 dwz: ./dwz.c:11021: build_abbrevs_for_die: Assertion `refd != NULL' failed. dh_dwz: error: dwz -mdebian/0ad/usr/lib/debug/.dwz/x86_64-linux-gnu/0ad.debug -M/usr/lib/debug/.dwz/x86_64-linux-gnu/0ad.debug -- debian/0ad/usr/games/pyrogenesis debian/0ad/usr/lib/games/0ad/ActorEditor debian/0ad/usr/lib/games/0ad/libAtlasUI.so debian/0ad/usr/lib/games/0ad/libCol
Bug#992017: Correct found versions
Control: notfound -1 0.0.23.1-2 Control: found -1 0.0.23.1-5+b1 Control: found -1 0.0.24b-1 Thanks -- Dave Kennedy
Bug#992017: New upstream release of 0ad - version 0.0.25
Package: 0ad Version: 0.0.23.1-2 Severity: wishlist Dear Maintainer, Version 0.0.25 of 0ad was just released. New Features in version 0.0.25 * Pathfinding and netcode improvements – improved pathfinding, performance and reduced game lag * Order restructuring – players can now push orders to the front of their production queues * Improved unit AI * New biomes incorporating 2K textures and normal/specular maps * Initial implementation of single player campaigns * GUI improvements * Extended graphics options * Improved mod support and game filtering in the multiplayer lobby * Ongoing civilization balancing * Various other game stability bug fixes and speedups Source is available at https://play0ad.com/download/source/ Build instructions are available at https://trac.wildfiregames.com/wiki/BuildInstructions Thanks. -- Dave Kennedy
Bug#978045: apache2-bin: Immediate exit with "AH00141: Could not initialize random number generator"
On Sat, Dec 26, 2020 at 10:37 PM Ondřej Surý wrote: > I believe it’s a reasonable assumption that the kernel matches the Debian > release. If anybody is running with old kernel or disables getrandom I > would say they are on their own - also other stuff will break, not only > apache2. > Yes, that makes sense. Surprisingly, although I've been putting off upgrading my kernel for a while, this was the first thing that broke - so far at least, everything else has fallbacks. I think a perfectly valid fix would be to document (in the changelog or elsewhere) that this hard requirement was added, in particular because (IIUC) using getrandom() instead of one of the other codepaths is the choice of the package maintainer. (I.e. this isn't just the result of upstream.) Tracking down what broke and why was mostly tricky because it wasn't documented, and Googling only turns up results on an unrelated Windows issue. > > This changed in libapr1 1.7, re-assigning to apr. I am not sure about > the severity, though. According to the man page, getrandom has been > introduced in linux 3.17. Debian 9 already has 4.9 so you have to have a > kernel that is from Debian 8 to be affected by this. > Sorry if the priority was overly high. I was going based on these descriptions from reportbug: 4 important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. 5 normal a bug that does not undermine the usability of the whole package; for example, a problem with a particular option or menu item. Based on that, "important" seemed more correct than "normal," since "won't even parse command-line options" is about as severe an effect on usability as it gets, but it was (likely) only affecting me. Looking at https://www.debian.org/Bugs/Developer#severities, normal is listed as "the default value, applicable to most bugs," and given that I'd categorize this as normal. -- =D ave
Bug#978045: apache2-bin: Immediate exit with "AH00141: Could not initialize random number generator"
Package: apache2-bin Version: 2.4.46-2 Severity: important On my machine, /usr/sbin/apache2 fails to start with the following message: [Thu Dec 24 15:38:01.052051 2020] [:crit] [pid 15725] (38)Function not implemented: AH00141: Could not initialize random number generator This happens very early, before reading conffiles or parsing command-line arguments. The error comes from line 5674 here: https://svn.apache.org/viewvc/httpd/httpd/trunk/server/core.c?revision=1884431&view=markup#l5674 and is due to a failure in apr_generate_random_bytes(). You can see that the associated call/failure is happening inside APR here, on line 216: https://svn.apache.org/viewvc/apr/apr/trunk/misc/unix/rand.c?revision=1832691&view=markup#l216 The issue is that if the library is configured (at build time) to USE_GETRANDOM, then it assumes that the getrandom() call will be available and if it fails it becomes a fatal error. On my system, I don't have getrandom() because I'm running an ancient kernel, but others could (more legitimately) have the option disabled on a recent custom-built kernel. I think the correct fix is to not use that build-time option, and go back to using DEV_RANDOM or whatever was being used previously. Alternatively, at least document that a kernel with getrandom() support is required to use apache2. I'm not sure exactly when the packaging on this changed, but I know it was broken in 2.4.46-1 and I *think* it worked in 2.4.43-1, although I can't get a copy of that to double-check anymore. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (501, 'testing'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14.15 (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apache2-bin depends on: ii libapr1 1.7.0-4 ii libaprutil1 1.6.1-5 ii libaprutil1-dbd-sqlite3 1.6.1-5 ii libaprutil1-ldap 1.6.1-5 ii libbrotli1 1.0.9-2+b2 ii libc62.31-5 ii libcrypt11:4.4.17-1 ii libcurl4 7.72.0-1 ii libjansson4 2.13.1-1 ii libldap-2.4-22.4.56+dfsg-1 ii liblua5.2-0 5.2.4-1.1+b3 ii libnghttp2-141.42.0-1 ii libpcre3 2:8.39-13 ii libssl1.11.1.1h-1 ii libxml2 2.9.10+dfsg-6.3+b1 ii perl 5.32.0-6 ii zlib1g 1:1.2.11.dfsg-2 apache2-bin recommends no packages. Versions of packages apache2-bin suggests: ii apache2-doc 2.4.46-2 pn apache2-suexec-pristine | apache2-suexec-custom ii links [www-browser] 2.21-1 ii lynx [www-browser] 2.9.0dev.6-1 ii w3m [www-browser]0.5.3-38+b1 Versions of packages apache2 depends on: ii apache2-data 2.4.46-2 ii apache2-utils2.4.46-2 ii dpkg 1.20.5 ii init-system-helpers 1.60 ii lsb-base 11.1.0 ii mime-support 3.66 ii perl 5.32.0-6 ii procps 2:3.3.16-5 Versions of packages apache2 recommends: ii ssl-cert 1.0.40 Versions of packages apache2 suggests: ii apache2-doc 2.4.46-2 pn apache2-suexec-pristine | apache2-suexec-custom ii links [www-browser] 2.21-1 ii lynx [www-browser] 2.9.0dev.6-1 ii w3m [www-browser]0.5.3-38+b1 Versions of packages apache2-bin is related to: ii apache2 2.4.46-2 ii apache2-bin 2.4.46-2 -- no debconf information
Bug#556987: so many wasted blank lines
Wrong EMAIL - Do not send to this email! From: "jida...@jidanni.org" To: 556...@bugs.debian.org Sent: Wed, March 10, 2010 5:57:32 AM Subject: Bug#556987: so many wasted blank lines B> - Use large screen/terminal to see overall description of each services. I'm using a 23 line high 7 inch EEEPC 702. I can see only 9 services at a time. Let's try aptitude. No lines wasted. All lines useful. Borders with maximum width 1. Emacs, vi, the same. I don't know why it is so important for the user to stare at all those blank lines in rcconf.
Bug#519555: "KNOWN PROBLEM" vs. 20/20 links
wrong email address
David.
Cell: 408-332-6189
From: Andrey Jr. Melnikov
To: 519...@bugs.debian.org
Cc: jida...@jidanni.org
Sent: Thursday, April 2, 2009 8:18:25 AM
Subject: Bug#519555: "KNOWN PROBLEM" vs. 20/20 links
Hello!
After apply this patch - I see 'hidden' services and can manage it.
Only need add 'functions' to unselects array.
--- /usr/sbin/rcconf2009-04-02 19:02:39.0 +0400
+++ /usr/sbin/rcconf.orig2009-04-02 19:02:32.0 +0400
@@ -617,7 +617,7 @@
( $rcdf->{$key}->[10] == $rcdf->{$key}->[14] ) &&
( $rcdf->{$key}->[10] == $rcdf->{$key}->[15] ) &&
( $rcdf->{$key}->[10] == $rcdf->{$key}->[16] ) &&
-( $rcdf->{$key}->[10] == 0 ) ) {
+( $rcdf->{$key}->[10] != -1 ) ) {
## defaults packages
push(@new_initd, $key);
}
without patch:
# rcconf --list | grep off
rsync off
mysql-ndb-mgm off
freshclam off
mysql-ndb off
font off
functions off
spamassassin off
clamd off
witch patch:
# rcconf --list | grep off
rsync off
pptpd off
mysql-ndb-mgm off
freshclam off
mysql-ndb off
font off
mysql off
functions off
spamassassin off
pxe off
clamd off
--
Best regards, TEMHOTA-RIPN aka MJA13-RIPE
System Administrator. mailto:temn...@kmv.ru
Bug#309369: more detail about apache not firing up.
i chose apache2-common figuring that would get it all started. once i added in apache2 it worked fine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#309369: Package: installation reports
Package: installation-reports Debian-installer-version: 20050514; http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc3/sarge-i386-netinst.iso uname -a: Linux ttc-12 2.6.8-2-386 #1 Mon Jan 24 03:01:58 EST 2005 i686 GNU/Linux Date: 20050514 3pm EDT Method: Installed, non-proxied, from ftp.uga.edu/linux/debian/dists/ ; with bootcd. Machine: Dell Poweredge 1800 Processor: 2.8 ghz Xeon 80546K Memory: 1 gig. Root Device: SATA WD-XL80SD-2 Root Size/partition table: sda1 Primary Linux swap / Solaris 1998.75 sda2Boot Primary Linux ext3 [/] 1497.01 sda5 Logical Linux ext3 [/boot] 98.71 sda6 Logical Linux ext3 [/usr]3997.49 sda7 Logical Linux ext3 [/var]3997.49 sda8 Logical Linux ext3 [/tmp]1497.01 sda9 Logical Linux ext3 [/home] 26913.12 Output of lspci and lspci -n: lspci: :00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 09) :00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0 (rev 09) :00:04.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port B0 (rev 09) :00:06.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port C0 (rev 09) :00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) :00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) :00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) :00:1f.2 RAID bus controller: Intel Corp. 82801EB (ICH5R) SATA (cc=RAID) (rev 02) :01:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09) :01:00.1 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller A (rev 09) :01:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09) :01:00.3 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller B (rev 09) :02:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08) :03:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) :06:05.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] lspci -n: :00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 09) :00:02.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port A0 (rev 09) :00:04.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port B0 (rev 09) :00:06.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port C0 (rev 09) :00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) :00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) :00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) :00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02) :00:1f.2 RAID bus controller: Intel Corp. 82801EB (ICH5R) SATA (cc=RAID) (rev 02) :01:00.0 PCI bridge: Intel Corp. PCI Bridge Hub A (rev 09) :01:00.1 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller A (rev 09) :01:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09) :01:00.3 PIC: Intel Corp. PCI Bridge Hub I/OxAPIC Interrupt Controller B (rev 09) :02:04.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X Fusion-MPT Dual Ultra320 SCSI (rev 08) :03:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) :06:05.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: System installs great; no probs there
