Re: Please give back ncbi-blast+ on mipsel and ppc64

2020-02-19 Thread Philipp Kern
On 2/19/2020 8:40 PM, Aaron M. Ucko wrote:
> As such, could we please try for another automated build?
> 
> gb ncbi-blast+_2.9.0-4 . mipsel

Looks like this already happened. FWIW with self-service giveback you
need to URL encode the plus but I confirmed that this works.

Kind regards
Philipp Kern



Re: Hurd-i386 and kfreebsd-{i386,amd64} removal

2019-04-13 Thread Philipp Kern
On 4/13/2019 12:49 PM, Aurelien Jarno wrote:
> The process to inject all packages to debian-ports is to get all the
> deb, udeb and buildinfo files from the archives (main and debug) and
> associate them with the .changes files that are hosted on coccia. We'll
> also need to fetch all the associated GPG keys used to sign the changes
> files. Then we can inject that in the debian-ports archive.
I'm curious how the GPG bit works given that there is no guarantee that
the signature can be validated at any other point in time than ingestion
on ftp-master - especially considering the rotation/expiry of subkeys
and buildd keys. In this case the files already come from a trusted
source and should be ingested as-is, I guess? (Not that I particularly
like the fact that it's only a point in time validation.)

Kind regards
Philipp Kern



Re: [Stretch] Status for architecture qualification

2016-06-16 Thread Philipp Kern

On 2016-06-15 00:37, Dimitri John Ledkov wrote:

There is openmainframe project https://www.openmainframeproject.org/ ,
which I believe offers access to z/VM instances hosted by Marist
colledge.

At the openmainframeproject EU meetup, it was indicated that SUSE
joined with indication that Open Build Service might be able to use
resources hosted by Marist.

I wonder if it makes sense to reach out, and see if there are
resources available to use as porter boxes & build boxes. That way
Debian might be able to get such donated resource available on ongoing
basis and hopefully with some hw support.


Debian already makes use of Marist's resources. The challenge was/is to 
get redundancy as DSA very sensibly insists on.


Kind regards
Philipp Kern



Re: [Stretch] Status for architecture qualification

2016-06-14 Thread Philipp Kern
On Mon, Jun 13, 2016 at 07:33:56PM +, Niels Thykier wrote:
> Philipp Kern:
> > On 2016-06-05 12:01, Niels Thykier wrote:
> >>  * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
> >>s390x
> >>- *No* blockers at this time from RT, DSA nor security.
> >>- s390, ppc64el and all arm ports have DSA concerns.
> > What is the current DSA concern about s390x?
> The concern listed as: "rely on sponsors for hardware (mild concern)"
> 
> As I recall the argument went something along the lines of:
> 
> "Debian cannot replace the hardware; if any of the machines dies, we
> need a sponsor to replace it.  If all of them dies and we cannot get
> sponsored replacements, we cannot support the architecture any longer"
> 
> (My wording)

Yeah, but that's unfortunately one of the universal truths of this port.
I mean in theory sometimes they turn up on eBay and people try to make
them work[1].

It also seems true for other ports where we commonly relied on sponsors
to hand us replacements. But maybe it's only ppc64el these days, maybe
there are useful builds available for the others (including arm64 and
mips) on the market now.

Kind regards and thanks
Philipp Kern

[1] https://www.youtube.com/watch?v=45X4VP8CGtk
(Here's What Happens When an 18 Year Old Buys a Mainframe)



Re: [Stretch] Status for architecture qualification

2016-06-07 Thread Philipp Kern

On 2016-06-05 12:01, Niels Thykier wrote:

 * amd64, i386, armel, armhf, arm64, mips, mipsel, powerpc, ppc64el,
   s390x
   - *No* blockers at this time from RT, DSA nor security.
   - s390, ppc64el and all arm ports have DSA concerns.


What is the current DSA concern about s390x?

Kind regards and thanks
Philipp Kern



Re: binNMUs: please exercise some care

2015-10-24 Thread Philipp Kern
On Fri, Oct 23, 2015 at 02:46:23PM +0200, Thorsten Glaser wrote:
> On Fri, 23 Oct 2015, Adam D. Barratt wrote:
> > and testing), so the only way to be certain what binNMU number to use is to
> > check manually. In practice what actually happens is that people forget 
> > about
> Maybe wb could do a “dak ls” and whatever the equivalent for dpo mini-dak is.

Unfortunately it is not being run on the same host as dak either.

Kind regards
Philipp Kern


signature.asc
Description: Digital signature


Re: Bits from the release team (freeze time line)

2013-12-28 Thread Philipp Kern
On Fri, Dec 27, 2013 at 02:19:07PM +0100, Andreas Barth wrote:
 However, using words like known-buggy mips* machines is just FUD
 against the mips*-ports, and plainly inacceptable, so please stop
 doing that. (For reference, there is no mipsel machine which has
 hardware bugs affecting daily operations. There are two mips machines
 which are pre-series and are not as stable as I wish, but as builddadm
 I was more occupied recently with arm* machines not stable then with
 mips machines not stable. This all doesn't mean I think nothing should
 be changed, but please do not FUD against mips* (or any other
 architecture).)

builddadm does not keep the machines running, DSA does. ball is ancient,
corelli and gabrielli are unstable under load and lucatelli does need
occasional reboots too, IIRC.

But mips and mipsel might not actually be the same bucket you'd want to
use, that seems to be the key takeaway here.

Kind regards
Philipp Kern


signature.asc
Description: Digital signature


Re: Qt5 switching qreal from float to double on arm*

2013-11-09 Thread Philipp Kern
On Thu, Nov 07, 2013 at 02:46:27PM -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:
 - If we decide to do the change in Qt5, it will be *without* soname bump. 
 Yes, 
 I know many of you will think of this as **ugly**, but so far means 3 binNMUs 
 per arch. Now if this is not acceptable, then no change will be made, because 
 I won't change Qt5's SONAME.

What is your plan to support partial upgrades? BinNMUs can require new Qt
versions to be installed, but Qt can be upgraded independently to the newer
version, causing the rdepends to crash. This can potentially be solved by
Breaks, but it still breaks assumptions of people using Debian in that such
ABI breaks will be communicated through SONAME bumps. And the old lib will
not even be coinstallable.

(Of course a good time to do such changes are in fact SONAME bumps, but I
realize that this won't happen for Qt for quite some time.)

Kind regards
Philipp Kern


signature.asc
Description: Digital signature


Fwd: mips uses cramfs

2012-02-21 Thread Philipp Kern
Hi,

I think the attached mail should go here, not to boot.

Kind regards
Philipp Kern
---BeginMessage---
Hi folks

The mips (not mipsel) images still uses cramfs. I intend to remove this
support from the kernel. All other linux arches uses initramfs.

If no one cries, I will change d-i as well, however I will not be able
to actually check it.

Bastian

-- 
A Vulcan can no sooner be disloyal than he can exist without breathing.
-- Kirk, The Menagerie, stardate 3012.4


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120221180214.ga28...@wavehammer.waldi.eu.org

---End Message---


signature.asc
Description: Digital signature


Re: Fwd: Bug#659294: [libarchive-discuss] Fwd: Bug#659294: libarchive: FTBFS on various architectures (hurd, mipsel, s390, s390x)

2012-02-11 Thread Philipp Kern
On Fri, Feb 10, 2012 at 04:34:40PM -0500, Andres Mejia wrote:
 Hi. The new version of libarchive uploaded to unstable is failing the
 test suite (and thus failing to build the deb packages). We're going
 to need copies of the test directories from the test suites, e.g.,
   Details for failing tests: /tmp/libarchive_test.2012-02-06T23.02.12-000
 Please provide these test directories to libarchive-disc...@googlegroups.com.

For s390(x) you can just use the porter box zelenka.  The build-deps are
installed.  For the other porterboxes you might need to mail the admin list to
get them installed.

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp KernDebian Developer
: :' :  http://philkern.de Stable Release Manager
`. `'   xmpp:p...@0x539.de Wanna-Build Admin
  `-finger pkern/k...@db.debian.org


signature.asc
Description: Digital signature


Meeting Minutes for the IRC Release Team Meeting on August 23, 2010

2010-08-23 Thread Philipp Kern
Hi there,

those are the minutes of Monday's IRC meeting at #debian-release.

1) What will be the release architectures for squeeze?
   - sparc will be kept as a release architecture for now.  The gcc code
 generation code which moved to v9/32bit has taken place in Nov 2009.
 There will be rebuilds of all packages that haven't been rebuilt
 since.  The exact details of this still need to be sketched out.
 [assignee: pkern]
   - mips*: #519006 is hurting us badly.  GCC upstream was pinged,
 Loongson and Codesourcery will be contacted about a backport to
 gcc-4.4 if there's no answer.  [assignee: aurel32]
   - mips: a possible toolchain issue popped up on openjdk-6,
 which needs investigation  [assignee: aurel32]
   - mipsel: another Loongson machine will be shipped to aba for
 use as a porter box  [assignees: zobel, aba]
   - hppa: HPPA will be dropped as a release architecture for squeeze.
 Details on a possible squeeze-hppa release need to be discussed
 with the hppa porters.  [assignee: ?]
   - kfreebsd-*: We consider a released kfreebsd-* package set as a 
 technology preview, that might not be up to the full Debian
 standards.  We will try to keep it in the same infrastructure
 set (i.e. as normal architectures) for squeeze, but this can be
 reviewed later.

2) Which transitions are left for squeeze?  What's their current state?
   - gnustep: RC bug on hppa, fix pending upload.  Looks good otherwise.
   - opencv: one FTBFS on hppa
   - ace: FTBFS on armel and kfreebsd, not a blocker
   - php: No transition removing deprecated features.
   - mono: mail to debian-release@ to be sent  [assignee: meebey]
   - apt: transition can be started in unstable  [assignee: mvo]
   - xapian: ditto  [assignee: olly]

3) Release Team meeting 2-3 October in Paris: Who's going?
   - Negotiations about times, crashing space and travel sponsorship
 need to be done with zack.  [assignee: faw]
   - mehdi, jcristau, luk, adsb, aba and pkern can probably make it;
 HE: unsure; faw: relying on the availabilty of overseas travel
 sponsorship, if not possible following remotely
   - Maulkin cannot make it.

4) What's the state of the Release Notes?
   - timeline: 4 weeks to get them ready, 2 weeks of string freeze, 1 week of
 fixes and final week for translations (i.e. 2 months)  [assignee: faw]
   - upgrade-reports to be prepared and solicited  [assignee: vorlon]

5) Any other business?
   - This item was not called as the time budget was exceeded.

A full log is available on [1] (text-only version on [2]).  Action and info
items are also available as extracted bits on [3].

Kind regards,
Philipp Kern
on behalf of the Debian Release Team

[1] 
http://meetbot.debian.net/debian-release/2010/debian-release.2010-08-23-20.02.log.html
[2] 
http://meetbot.debian.net/debian-release/2010/debian-release.2010-08-23-20.02.log.txt
[3] 
http://meetbot.debian.net/debian-release/2010/debian-release.2010-08-23-20.02.html


signature.asc
Description: Digital signature