=== blitz_ is now known as blitz [20:16] pleia2, do you happen to know what mailing list would be the correct one to ask about the google code shutdown and what that will mean for the project website links shown by apt-cache show or the view homepage link in synaptic [20:17] ianorlinhex: ubuntu-devel-discuss@lists.ubuntu.com [20:17] ubuntu-devel is probably ok too, but all messages from non-confirmed devs get moderated and they don't always empty the queue in a timely manner [20:18] https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss [20:18] Title: [Ubuntu-devel-discuss Info Page] [20:18] just make sure you're subscribed to post :) [20:19] I'm hopeful that the package maintainers will update their packages with the new URLs, but of course that won't happen immediately and likely won't at all for past releases (including the LTS releases) [20:19] maybe google code will offer a redirection service [20:19] (hah) [20:20] I think they did offer that I mean I sometimes find bugs in that that they have moved the website even without a site shutting down [20:20] or they don't update the link in the manpage or in ui under help about [20:20] hard to remember every link in the that many packages [20:22] well, each package in debian has a maintainer, so that maintainer should pay attention [20:22] in Ubuntu-specifically they are managed by package teams, which I hope have some more coodination and could go through their sets to update things, compared to the amount they pull in from Debian it's small [20:45] ianorlinhex: I would probably file bugs against the Debian packages if you notice this applies to them. Personally, I would be more worried about out-of-date debian/watch files (those are used by some tools to notify the maintainer that a new upstream version of the package is available) [20:47] nhandler, yeah I ended up taking a shower and thinking the same thing [20:48] as getting fixed upstream fixes everyone and ubuntu maintainers don't have to worry about tiny patchsets across many different packages