Custom Query (1145 matches)
Results (49 - 51 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #67 | fixed | MIT CA certificate should be managed by update-ca-certificates | andersk | |
| Description |
The current debathena-ca-certificates package links mitCA.pem directly into /etc/ssl/certs and runs c_rehash. However, many applications miss the new CA because they only look at /etc/ssl/certs/ca-certificates.crt, which is a bundle of certificates managed by update-ca-certificates. A better way to install the CA is to package it as /usr/share/ca-certificates/mit.edu/mitCA.crt, and run dpkg-reconfigure ca-certificates. This will prompt the user to trust the new CA, upon which it will be linked into /etc/ssl/certs and added to /etc/ssl/certs/ca-certificates.crt. We should figure out how to make this happen without prompting the user, while still preserving other changes to ca-certificates and allowing clean uninstallation. |
|||
| #68 | fixed | AUTO_UPDATE_AUTOCONF should be a version number (2.13 or 2.50), not 1 | andersk | |
| Description |
Most of our packages have the line "AUTO_UPDATE_AUTOCONF = 1". It should actually be a version number, such as "AUTO_UPDATE_AUTOCONF = 2.50" or "AUTO_UPDATE_AUTOCONF = 2.13", because CDBS runs
|
|||
| #69 | fixed | DEB_AUTO_UPDATE_DEBIAN_CONTROL displeases the gods of Debian | andersk | |
| Description |
As described in Debian #311724, Debian doesn't like the DEB_AUTO_UPDATE_DEBIAN_CONTROL feature that modifies debian/control at build time. We might consider removing it from our debian/rules files and only invoking it manually with
Even if we decide not to remove it, we should probably change its value from "1" to "yes" because the documentation suggests that is more conventional. |
|||
