Custom Query (1145 matches)
Results (79 - 81 of 1145)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #561 | fixed | DEB_AUTO_UPDATE_DEBIAN_CONTROL also displeases mortals | broder | geofft |
| Description |
Nobody can remember what the syntax for manually generating debian/control from debian/control.in is (this is especially confusing to new developers, or non-Debathena folks trying to compile/reuse our code), it's in a number of cases the only thing that makes our version control repository differ from our source packages, and there are a couple of screw cases where [r24514 DEB_AUTO_UPDATE_DEBIAN_CONTROL can't be made to work] even if we wanted to. We should get rid of our use of DEB_AUTO_UPDATE_DEBIAN_CONTROL/control.in, because it's not buying us all that much compared to the inconsistencies and usability issues it introduces. For the sake of not patching every package at separate times, Evan wants to do this when #481 and #560 get done. |
|||
| #573 | fixed | gdm-config undiverted xsplash and throbber incorrectly | broder | broder |
| Description |
When I updated the gdm theming, I tried to undivert /usr/share/images/xsplash/bg_2560x1600.debathena.jpg and /usr/share/images/xsplash/throbber_{small,medium,large,xtra_large}.debathena.png. Unfortunately, I got my conditionals backwards and undiverted the files for old gdm instead of new gdm. This means that Hardy/Intrepid/Jaunty/Lenny? users get a spurious OMINOUS WARNING, while Karmic/Lucid/Squeeze? users don't get the stale diversion removed. This should get cleaned up. Unfortunately, since config-package-dev doesn't account for the scenario where the developer screws up, we can't use config-package-dev to remove these diversions anymore, and we'll have to use cleanup_old_diversion by hand in the postinst. |
|||
| #601 | fixed | apparmor homedirs should include /afs/athena/user/*/*/ | gdb | geofft |
| Description |
I'm seeing this sort of thing in dmesg on debathena-workstation on Karmic: [1092648.801173] type=1503 audit(1275579304.532:1014): operation="mknod" pid=12569 parent=1 profile="/usr/bin/evince" requested_mask="w::" denied_mask="w::" fsuid=40490 ouid=40490 name="/afs/athena.mit.edu/user/g/e/geofft/.recently-used.xbel.LUR1DV" [1092650.215497] type=1503 audit(1275579305.945:1015): operation="truncate" pid=12569 parent=1 profile="/usr/bin/evince" requested_mask="w::" denied_mask="w::" fsuid=40490 ouid=40490 name="/afs/athena.mit.edu/user/g/e/geofft/.gnome2/evince/ev-metadata.xml" /etc/apparmor.d/usr.bin.evince uses @{HOME} in a couple of places, and includes, eventually, /etc/apparmor.d/tunables/home, which has the following two rules: @{HOME}=@{HOMEDIRS}/*/ /root/
@{HOMEDIRS}=/home/
I think it makes sense to add Athena AFS homedir paths to @{HOMEDIRS}. But I'm kind of hesitant to suggest changes to AppArmor? config in general... |
|||
