Re: [HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1

2013-03-20 Thread Jeremy Chadwick
On Wed, Mar 20, 2013 at 04:20:02PM +0100, Matthias Gamsjager wrote:
> >  Due to the security incident, there are still no official FreeBSD
> > packages.
> 
> Do you know what the status is on that issue?

I'd also like to find out what the status of this is.

The packages at:

ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/

Are still circa October 2012 -- that's 4-5 months ago.

While I truly and deeply understand that proper engineering design and
infrastructure changes take time, there has been absolutely no
communication presented to the community as to what has (or hasn't)
transpired, if there is (or isn't) a plan, or if people are simply
waiting until future in-person BSD* events to work things out.
freebsd-ops-announce has been silent on this matter as well:

http://lists.freebsd.org/mailman/listinfo/freebsd-ops-announce

At this point users and administrators do not know if newer packages
will be made available or if they should stick to building purely from
source.

Deep down I'm worried that this will solicit a response of "switch to
ports-mgmt/pkg and ports-mgmt/poudriere".  While I'm not opposed to the
tools themselves, I'm strongly opposed to that kind of response as I'm
tired of seeing the security incident being used as a opportunistic
crutch (as it was for the sudden cvsup/csup deprecation).

-- 
| Jeremy Chadwick   j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: [HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1

2013-03-20 Thread Matthew Seaman
On 20/03/2013 15:20, Matthias Gamsjager wrote:
>>  Due to the security incident, there are still no official FreeBSD
>> packages.
>>
> 
> 
> Do you know what the status is on that issue?

Unchanged so far.  No official pkgng packages yet.

However, an end to the wait is apparently in sight.  There has been
mention of work on pkgng building systems.

Cheers,

Matthew

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


Re: [HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1

2013-03-20 Thread Matthias Gamsjager
>  Due to the security incident, there are still no official FreeBSD
> packages.
>


Do you know what the status is on that issue?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


[HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1

2013-03-14 Thread Bryan Drewery
This only affects binary-packages-only users.

pkg 1.0.9 had a regression with 'pkg update' that will prevent
updating your repository. Please skip this version and use 1.0.9_1.


This version was only in ports for 7 hours. Due to the security
incident, there are still no official FreeBSD packages. If you are
using an unofficial mirror, it is unlikely it would have upgraded to
1.0.9 in the time it was in the tree.

If you are building your own packages and managed to get onto 1.0.9
you can upgrade to 1.0.9_1 as follows:

# cp /usr/local/sbin/pkgs-static .
# pkg delete -f pkg
# ./pkg-static add URL-TO-YOUR-PACKAGESITE/All/pkg-1.0.9_1.txz
#optional
# rm pkg-static


As for how this managed to get released. We did do a functional
test of this before releasing, but due to the nature of 'pkg update'
using a cache, it was not immediately obvious that it was broken.

We do need your help with adding more automated tests.
http://lists.freebsd.org/pipermail/freebsd-pkg/2013-March/16.html
has our call for help on this front and more information.


Regards,
Bryan Drewery




signature.asc
Description: OpenPGP digital signature