Page MenuHomePhabricator

Track source of packages in reprepro
Closed, ResolvedPublic

Description

In our custom apt repositories we have...

  • Packages built from gerrit that we wrote
  • Packages built from gerrit where the code in gerrit is a fork
  • Packages built from upstream source, nothing in gerrit
  • Packages we didn't built but just grabbed from another source

Reprepro doesn't know where they came from, or care. So... it would great to have a systematic system for recording where a given package came from, who built it, and how it was built.

Event Timeline

Andrew raised the priority of this task from to Needs Triage.
Andrew updated the task description. (Show Details)
Andrew added a project: acl*sre-team.
Andrew subscribed.

when built from upstream source they should be in component universe. if we made them all ourselves they should be in component main. i think they should always be in gerrit unless there is a really good reason not to?

per https://wikitech.wikimedia.org/wiki/Reprepro

main

for Wikimedia native packages, as well as Debian/Ubuntu packages that have had source-modifications

universe

for existing Debian/Ubuntu packages that just have been recompiled/backported for the given distribution.

sometimes we have this mixed up for different versions of the same package,

example:

http://apt.wikimedia.org/wikimedia/pool/main/a/adminbot/

vs.

http://apt.wikimedia.org/wikimedia/pool/universe/a/adminbot/

it would be nice to systematically check for this and merge them all into the proper component

fgiunchedi renamed this task from Track source of packages in repro to Track source of packages in reprepro.Jul 20 2015, 2:17 PM
fgiunchedi triaged this task as Low priority.
fgiunchedi set Security to None.

agreed it would be nice, one way to do this would be to map the source package name with the expected component. Then we can audit what's in reprepro and upload packages in their expected component

the same map could be also used to aid jenkins build debian packages for us

MoritzMuehlenhoff claimed this task.
MoritzMuehlenhoff subscribed.

This task is quite old and these days we've established the scheme of using separate components which allow mapping package/external sources to repository components. Marking as resolved.