New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move DEB_AUTO_UPDATE_DEBIAN_CONTROL out of Debian packages #3029
Comments
Attachment: auto-update-debian-control.patch.gz |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:3
Hi Tim, do I still need to run the perl script if I apply the patches? I would prefer to import 25 patches since then I do have a record. Since I will likely touch a lot of the spkgs in the next two days for cleanups I think it will be fine if you post those 25 patches and I just merge them as I go. Cheers, Michael |
comment:4
No, the perl script is what generates the patches that need to be done (there's also a single patch not done by the perl script that I've already uploaded). I'll go ahead and post the 25 patches, then. |
Attachment: auto-cddlib.patch.gz |
Attachment: auto-extcode.patch.gz |
Attachment: auto-flint.patch.gz |
Attachment: auto-flintqs.patch.gz |
Attachment: auto-genus.patch.gz Attachment: auto-gfan.patch.gz |
Attachment: auto-givaro.patch.gz Attachment: auto-iml.patch.gz |
Attachment: auto-jmol.patch.gz |
Attachment: auto-libfplll.patch.gz |
Attachment: auto-libm4ri.patch.gz |
Attachment: auto-linbox.patch.gz Attachment: auto-palp.patch.gz |
Attachment: auto-rubiks.patch.gz |
Attachment: auto-singular.patch.gz |
Attachment: auto-symmetr.patch.gz |
Attachment: auto-sympow.patch.gz Attachment: auto-tachyon.patch.gz |
Attachment: auto-zn_pol.patch.gz Attachment: auto-scipy_sandbox.patch.gz |
Attachment: auto-ntl.patch.gz |
Attachment: auto-polybori.patch.gz |
Attachment: auto-gap.patch.gz |
comment:5
The patches look good to me. Most of them are really trivial, the two, three others are fine, too. I put them into the spkgs without bumping the patch level to avoid massive recompile on update. Please, no more massive 25 spkg patch orgies ;) Cheers, Michael |
comment:6
Merged in Sage 3.0.1.alpha1 |
Debian doesn't allow you to upload packages that use DEB_AUTO_UPDATE_DEBIAN_CONTROL because it causes confusion with Non-Maintainer Uploads. Since I'd like to get the packages so that they can be uploaded to Debian, we should remove it from our rules files. Since it's fine for our purposes, I've modified sage-debsource to set DEB_AUTO_UPDATE_DEBIAN_CONTROL so that it always gets used when we are building packages. I think it's probably easier for Michael to just make the changes than to merge N patches, so the following code will do the relevant update when the relevant spkgs are unpacked.
(if the patches are easier to deal with, let me know and I'll generate them)
The complete list of spkgs that require this treatment is as follows:
Component: debian-package
Issue created by migration from https://trac.sagemath.org/ticket/3029
The text was updated successfully, but these errors were encountered: