Parsix apt repository

[pabs]

I wasn't able to get Alan to respond to email, so maybe he will read this before his email. Alan, please respond to these two posts (I'm not subscribed to the list, so please CC me):

http://lists.parsix.org/pipermail/parsi ... 02499.html
http://lists.parsix.org/pipermail/parsi ... 02500.html

[alan]

Thanks!

The repo needs a bit of clean-up. I'll add the SHA check-sums for version 4.0 with a newer reprepro package. The forbidden errors are because of mod-security module on Apache. Just retry to run apt-get update and it should work fine.

Would you like to join me for development?

Alan

[pabs]

I tried doing apt-get update again but I just get more errors. This mod-security thing means I will get a lot of email about things failing, so it would be great if you could remove whatever limits are being hit by apt updates, otherwise it will be very annoying.

Good to hear you will fix the hash issues, thanks!

I'm only here because someone added Parsix to the Debian derivatives census:

http://wiki.debian.org/Derivatives/Census/Parsix
http://wiki.debian.org/Derivatives/Census

It would be great if you or another Parsix developer could sign up to maintain that wiki page and fill in any applicable missing parts.

It would be great if you could respond to email in future. Do you read your email account?

I tried to contact you on the #parsix IRC channel but I had no luck there.

I would like to invite you to join the #debian-derivatives IRC channel on OFTC and the debian-derivatives mailing list:

http://wiki.debian.org/DerivativesFrontDesk

[alan]

Hi,

OK, Regarding:

http://lists.parsix.org/pipermail/parsi ... 02499.html

Most of missing files are on wonderland repo which is a sync of debian-multimedia. We don't touch that repo. It is just a mirror. So somebody needs to notify them.

I'll check to see why that particular source package file is missing.

Thanks.

[pabs]

I'm still getting those 403 errors, did you get a chance to look at the mod-security configuration?

Also the qgtkstyle source tarball is still missing (as well as the wonderland stuff).

[alan]

Hey,

Let me know if you still get 403 errors.

I fixed and re-uploaded the source package for qgtkstyle. Also removed deprecated lists files of wonderland repo which belonged to Parsix Vinnie. You should not see those 404 errors anymore.

Let me know how it goes.

Thanks,
Alan

[pabs]

I still get 403 errors on the Packages files.

Your apt repository is missing a lot of SHA-1 and SHA-256 checksums:

http://dex.alioth.debian.org/census/Par ... ckage-list

If you are using reprepro, then very recent versions include a redochecksums command. If you are using something else then you might need to get that tool fixed, please file a bug.

All the other issues are fixed, thanks!

[pabs]

BTW, I've been looking at the patches applied by Parsix:

http://dex.alioth.debian.org/census/Parsix/patches/

I found some packages with various issues:

Where the source package is absolutely identical to the Debian one, but it has been rebuilt so the checksums don't match. It would be better if you just use the Debian version, so that our patch scripts do not have to spend CPU time comparing identical source packages.

Where the only change is to the debian/changelog file. Same issue with wasting CPU time, shouldn't you just upload the same source package to Parsix without changing debian/changelog?

Packages with changes that haven't been forwarded to Debian. Please always file a Debian bug when you package a new upstream release or fix a homepage field or whatever else. For example the balsa package in Parsix got update, but balsa in Debian has a request for help bug open, you could help out.

[alan]

Our build system is designed to grab the source from upstream for packages we build internally. Reason for modifying debian/changelog only in some cases is that some of our packages have a different version number (extra epoch or missing epoch) so we have to make it compatible with ours.

[pabs]

I'm still getting those 403 errors, could you investigate that?

If it helps, you could whitelist these IP addresses, thats where I plan to run the scripts:

206.12.19.122
217.196.43.132
217.196.43.134

[pabs]

I am no longer getting 403 errors from the apt repository, thanks for fixing that!

[alan]

Cool! thanks.