Re: jessie-kfreebsd package in Uploaded, not Installed state?

[Steven Chamberlain]

Christoph Egger wrote:
> Afair I can loginto the buildd, rename the changes file there and
> upload.

It still hasn't installed.  Shall I just upload a new version?

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Re: jessie-kfreebsd package in Uploaded, not Installed state?

[Christoph Egger]

Hi!

Steven Chamberlain  writes:
> Christoph Egger wrote:
>> Afair I can loginto the buildd, rename the changes file there and
>> upload.
>
> It still hasn't installed.  Shall I just upload a new version?

Seems I need to refresh the signature as well as rename the file. Should
hopefully be handled now

  Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer

Re: jessie-kfreebsd package in Uploaded, not Installed state?

[Cyril Brulebois]

(trimming recipients list a bit)

Christoph Egger  (2015-11-10):
> Steven Chamberlain  writes:
> > Pretty smart!  That's exactly what I did.  I often build with
> > `dpkg-buildpackage -g` but somehow never saw this problem before,
> > in sid for example.  Maybe it is only an issue in -proposed-updates.
> >
> > Is it something easily fixed without doing a binNMU or uploading a
> > new version?  The file in the way is:
> > ftp://ftp.debian.org/debian/dists/jessie-kfreebsd-proposed-updates/kfreebsd-10_10.1%7Esvn274115-4+kbsd8u1_kfreebsd-amd64.changes
> 
> Afair I can loginto the buildd, rename the changes file there and
> upload. Probably Cyril can also do that. I'll just try.

No I cannot, I had my buildd credentials revoked when I stepped down as a
buildd maintainer a tiny while ago. ;-)

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: jessie-kfreebsd package in Uploaded, not Installed state?

[Cyril Brulebois]

Hi,

Steven Chamberlain  (2015-11-10):
> Hi Christoph and/or FTP masters,
> 
> I made a source+arch:all upload of kfreebsd-10 to the jessie-kfreebsd
> suite.  It built on the kfreebsd-amd64 and -i386 buildds, but on -amd64
> it has stayed in Uploaded state, not Installed?  Why might that happen?
> https://buildd.debian.org/status/package.php?p=kfreebsd-10=jessie-kfreebsd

You probably uploaded a _kfreebsd-amd64.changes file for source+all, and
that filename being already taken for your upload, the buildd can't
reuse the same filename?

> I also made uploads of anna and netcfg which had no problems:
> https://buildd.debian.org/status/package.php?p=anna=jessie-kfreebsd
> https://buildd.debian.org/status/package.php?p=netcfg=jessie-kfreebsd

Those don't contain any arch:all packages, so you probably only uploaded
a _source.changes file?

(Too lazy to check right now; hopefully my first guess is OK…)

Mraw,
KiBi.


signature.asc
Description: Digital signature

Re: jessie-kfreebsd package in Uploaded, not Installed state?

[Steven Chamberlain]

Hi,

Cyril Brulebois wrote:
> Steven Chamberlain  (2015-11-10):
> > I made a source+arch:all upload of kfreebsd-10 to the jessie-kfreebsd
> > suite.  It built on the kfreebsd-amd64 and -i386 buildds, but on -amd64
> > it has stayed in Uploaded state, not Installed?  Why might that happen?
> > https://buildd.debian.org/status/package.php?p=kfreebsd-10=jessie-kfreebsd
> 
> You probably uploaded a _kfreebsd-amd64.changes file for source+all, and
> that filename being already taken for your upload, the buildd can't
> reuse the same filename?

Pretty smart!  That's exactly what I did.  I often build with
`dpkg-buildpackage -g` but somehow never saw this problem before,
in sid for example.  Maybe it is only an issue in -proposed-updates.

Is it something easily fixed without doing a binNMU or uploading a
new version?  The file in the way is:
ftp://ftp.debian.org/debian/dists/jessie-kfreebsd-proposed-updates/kfreebsd-10_10.1%7Esvn274115-4+kbsd8u1_kfreebsd-amd64.changes

I guess the file is needed later for migration to -stable, so can't be
deleted, but maybe it can be renamed to *_multi.changes for example?

> > I also made uploads of anna and netcfg which had no problems:
> > https://buildd.debian.org/status/package.php?p=anna=jessie-kfreebsd
> > https://buildd.debian.org/status/package.php?p=netcfg=jessie-kfreebsd
> 
> Those don't contain any arch:all packages, so you probably only uploaded
> a _source.changes file?
> 
> (Too lazy to check right now; hopefully my first guess is OK…)

You were right about that too.

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Re: jessie-kfreebsd package in Uploaded, not Installed state?

[Christoph Egger]

Steven Chamberlain  writes:
> Pretty smart!  That's exactly what I did.  I often build with
> `dpkg-buildpackage -g` but somehow never saw this problem before,
> in sid for example.  Maybe it is only an issue in -proposed-updates.
>
> Is it something easily fixed without doing a binNMU or uploading a
> new version?  The file in the way is:
> ftp://ftp.debian.org/debian/dists/jessie-kfreebsd-proposed-updates/kfreebsd-10_10.1%7Esvn274115-4+kbsd8u1_kfreebsd-amd64.changes

Afair I can loginto the buildd, rename the changes file there and
upload. Probably Cyril can also do that. I'll just try.

  Christoph

-- 
9FED 5C6C E206 B70A 5857  70CA 9655 22B9 D49A E731
Debian Developer | Lisp Hacker | CaCert Assurer

jessie-kfreebsd package in Uploaded, not Installed state?

[Steven Chamberlain]

Hi Christoph and/or FTP masters,

I made a source+arch:all upload of kfreebsd-10 to the jessie-kfreebsd
suite.  It built on the kfreebsd-amd64 and -i386 buildds, but on -amd64
it has stayed in Uploaded state, not Installed?  Why might that happen?
https://buildd.debian.org/status/package.php?p=kfreebsd-10=jessie-kfreebsd

I also made uploads of anna and netcfg which had no problems:
https://buildd.debian.org/status/package.php?p=anna=jessie-kfreebsd
https://buildd.debian.org/status/package.php?p=netcfg=jessie-kfreebsd

Thanks,
Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature