Creating a debian repository for squeeze and lenny

Hi guys,

Our company hosts packages of our own software on a local repository on our network. Right now it is what this guide refers to as a "trivial repository"

Our current development platform is Debian lenny, but we'd like to move to Debian squeeze. The problem is that our product's custom made packages, which we put into our local repo, are not compatible between the two. I have to tweak some dependencies and there are some minor code changes needed to make it work on squeeze.

Ideally, I'd like to make a fork of our project just for squeeze, and build "squeeze" specific packages.

How can I change the repository so that I have one set of "lenny" packages available for lenny machines, and another set of "squeeze compatible" packages are available for squeeze machines?

Below is an example of my sources.list:

deb lenny main
deb-src lenny main
# our local repository
deb binary/

Open in new window

And an example of the tree structure in our Repo:

|-- binary
|   |-- Packages
|   |-- Packages.gz
|   |-- ourproduct_10.10-3057_all.deb
|   |-- ourproduct_10.11-3068_all.deb
|   |-- ourproduct_11.0-3160_all.deb
|   |-- ourproduct_11.2-3174_all.deb
|   |-- ourproduct_12.1-3188_all.deb

Open in new window

You can see how unlike the regular debian repos, our local one doesn't explicitly say "lenny" on it anywhere - so those packages show up no matter what version of linux we're using.

How do I change our local repository and/or my sources file so that I can make packages that differentiate between lenny and squeeze?
LVL 31
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

nociSoftware EngineerCommented:
What is wrong in using automatic repositories from that same document?

You can follow this URL to see how debian does it..

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Frosty555Author Commented:
Is creating the appropriate directory structure all that is necessary? I don't need to do any other fancy configuration of the package or anything like that?
nociSoftware EngineerCommented:
it needs to be built for every environment of course.
And that might be more tricky than you think. If you need some feature from a library that is different from one set to another, that might give you a challenge.

(I used to have such problems in the past with RedHat, they provide a long term stable platform, but sometimes i need a faster moving platform and then there are conflicting libraries, depending on the mixed you need).
Esp. openssl might break between versions (by design, to prevent continued use of defective libraries).
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.