Custom Query (1145 matches)
Results (208 - 210 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #552 | fixed | auto-update should set UCF_FORCE_CONFFNEW on -cluster | broder | |
| Description |
On cluster machines, auto-update should set UCF_FORCE_CONFFNEW for the same reason we're passing --force-confnew. |
|||
| #554 | wontfix | auto-update should refuse to run if -development is enabled | broder | |
| Description |
The rules for -development and the rules for auto-update conflict with each other. auto-update assumes a world with apt repository semantics, where version numbers are monotonically increasing. -development assumes a world where things can be arbitrarily broken, and where we don't have to fix them later, where there's no guarantee we won't scribble over your harddrive, and where version numbers are convenient labels that we can change and re-write as we please. This does bad things when, say, I upload a package to -development specifically because I expect it to break things, and then auto-update goes and installs it on a bunch of workstations. auto-update should refuse to run if -development is enabled, because there are simply no guarantees that the end result will be a sane one. |
|||
| #565 | fixed | We don't write maintainer scripts for the #PACKAGE# package | broder | |
| Description |
The template maintainer scripts in /usr/share/debhelper/dh_make/debian have a #PACKAGE# marker in them. Normally that gets filled in by dh_make, but if you don't use dh_make and copy the template by hand (or copy it from another package), you should replace #PACKAGE# with the actual package name. We've forgotten to do this a whole bunch of times; we should hunt them down and clean them up. |
|||
