-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Den 03. nov. 2014 20:13, skrev Andreas Beckmann: > On 2014-11-03 20:04, Adam D. Barratt wrote: >> That might be true if the fix could wait until the next stable >> point release (unplanned yet, but at the earliest in >> mid-December). Aside from anything else, at least this SRM will >> be following standard procedure and not acking the wheezy fix >> until at least unstable is fixed in any case. > > Unstable/jessie would not really need that fix (it's a > squeeze->wheezy upgrade issue), but it won't harm :-) > > @Andreas Noteng: So lets get the fix into sid. Same changelog as > for 3.0.1-1+deb7u1, but version it again as 3.0.1-2 and target > unstable. Upload to mentors and send me the link to the .dsc >
Thanks for the upload. Wouldn't it be just as easy to upload the 3.1.0-1 package to unstable right away? If the release team agrees with the unblock for testing or not, I still want the updated package to go into unstable. Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJUV9xGAAoJELRG7qgympRacC0QAI1RihnhVV+ityqyFzNGgW39 OuTaN0QLKaWqHAgunsB9rip1aOhVlObeCRtYNSS/Drcx4amgNPgotjPu14MRGOuu WP47ks9kOAvL9JGh+n6mGcBmcCXMyyaKIcIHqhk+IgwB0+/JOYApzpvM/flt30mT zEPBnFfe1eqNVH/IVKFzgaWwPWqFdLA6uX9Ua7OhQrBYCYQdCwRkv7/B5QClbnqt SYe/Vz+5baRY/3raMQ8yPt6KB4yRLKE9n73QwZSHmOgazgtIv03clDx/fJk3zpwQ hAMCkAJgbFVTFW3I/mkv1u22mf6dbj0SA2aYesk9IcZp0dS4n3f4cZ3dG15xeeKW FqrnOEt/fr0W2bm4UA0CA8a++SKsykF98wMkRd81dgAZmYouvVPkpwIWMdFJTqmV ZrOiVR8aKfUWuAN8FMUXgviAiA0ffCT75BB42Cxkf7w5f7n+dxdQqWgA0KlATlaK KcHm9emJpZKVeyP/nOFWuqPicN1kRPEjvfCN7kczWmr+txMDeHuzH86un18I+JrC 7fjVX8QB/7HzEGRQ8iHH0OGP1qscSeW01+Zzb4CjT/RpZijMKhsHxmQMjEMz4nfx oT7jtyY9N0xmyDFVxBVzfygm92Fi7RV99MuBrv8bFcQyjpOmRnrfPv5dHf17Ok+q EmPWkcQTMFOL5wHmWBIx =R9pk -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
