Project

General

Profile

Feature #2426

precise packages for apache2, fastcgi

Added by Sage Weil about 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
% Done:

0%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

History

#1 Updated by Sage Weil about 8 years ago

Either set up a gitbuilder, or build the packages manually and put in a repo, or just use the dho packages+repo (built manually).

#2 Updated by Sage Weil about 8 years ago

Ok, I just rsynced the dho packages (manually built) over to the gitbuilder url. At the very least, need to document where the package sources are so they can be adjusted later.

#3 Updated by Sage Weil about 8 years ago

  • translation missing: en.field_position deleted (1)
  • translation missing: en.field_position set to 18

#4 Updated by Sage Weil about 8 years ago

  • translation missing: en.field_story_points set to 2
  • translation missing: en.field_position deleted (17)
  • translation missing: en.field_position set to 17

#5 Updated by Sage Weil about 8 years ago

  • Target version set to v0.48
  • translation missing: en.field_position deleted (10)
  • translation missing: en.field_position set to 1246

#6 Updated by Dan Mick about 8 years ago

  • Assignee set to Dan Mick

#7 Updated by Sage Weil about 8 years ago

Pretty sure i built this on pudgy, whose disk has just died.

I'd apt-get source these and verify we can rebuild these packages, and then call this done. Sometime soon we will need to build a fastcgi package without the patch in there that dumps the full environment for every request... let's make sure we can do that easily.

#8 Updated by Dan Mick about 8 years ago

So I've built the packages from the git repo versions (not source, but binary) and they install on my
precise desktop without security complaint. I haven't yet located anything that can actually validate the signature and print a response; dpkg-sig is just silent about the package or the .changes file.
Maybe I could uninstall the Ceph key and try installing?...really unclear that the signature
is effective. I do see the PGP marks in .changes. ???

#9 Updated by Sage Weil about 8 years ago

Iiuc its apt and not dpkg that checks sigs. Creating and signing a repo and pointing apt at it is enough to generate the warnings. It sounds like its all set tho... let's double check tomorrow and then close this out!

#10 Updated by Dan Mick about 8 years ago

  • Status changed from New to Resolved

OK, I think the packages are workable now.

Also available in: Atom PDF