pixfrogger 1.0-4 is available in Ubuntu 16.10:
https://launchpad.net/ubuntu/+source/pixfrogger/1.0-4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585058
Title:
Sync pixfrogger 1.0-4 (universe)
** Changed in: pixfrogger (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585058
Title:
Sync pixfrogger 1.0-4 (universe) from Debian unstable
The package indeed built fine, the problem is that it is not migrating
out of -proposed because it is not installable on amd64. I'm not sure
why this is a problem given that the package in -release isn't
installable on amd64 either, but I guess it's an odd situation. In any
case I think this needs
Isn't that the entire point of introducing the XS-Build-Indep-
Architecture field in d/control? I assumed that https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=534063#16 implied Ubuntu's infrastracture
supports it now...
--
You received this bug notification because you are a member of Ubuntu
> 1.0-2 and earlier never had problems migrating from proposed;
> pixfrogger has always been arch:all.
pixfrogger 1.0-2 was built on Karmic and back then Arch:all packages were built
on i386.
Now Arch:all packages are built on amd64. I don't know of a solution.
--
You received this bug
Ubuntu Archive Administrators,
What needs to be done for this package to migrate out of -proposed? The
package does not pass the piuparts check, but Vincent has a decent
argument for why he believes the package should be Arch:all and not
Arch:i386 like I suggested. See
1.0-2 and earlier never had problems migrating from proposed; pixfrogger
has always been arch:all.
As for declaring pixfrogger arch:i386, I've replied to that suggestion
at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534063#36
--
You received this bug notification because you are a member
>From looking at the publishing history, it looks like version 1.0-3 and
1.0-3ubuntu1 also got stuck in -proposed
Since pixfrogger is only installed on i386, why not try declaring the
binary pixfrogger as Architecture: i386?
By doing so, I wouldn't think you would need the XS-Build-Indep-
Pixfrogger is an arch:all package that has dependencies (fenix) that are
not installable on amd64, so yes, that's expected. (This upload fixes
https://bugs.debian.org/534063 which ensures that the package is only
built on archs that support all its build-deps to prevent FTBFS bugs,
but it doesn't
I synced the package, but apparently it is not installable on amd64,
search for pixfrogger on http://people.canonical.com/~ubuntu-archive
/proposed-migration/yakkety/update_excuses.html -- is this expected?
What should be done about it?
** Changed in: pixfrogger (Ubuntu)
Status: Fix
This bug was fixed in the package pixfrogger - 1.0-4
Sponsored for Vincent Cheng (vincent-c)
---
pixfrogger (1.0-4) unstable; urgency=medium
* Team upload.
* Declare the architecture affinity to handle build-dependency on a package
which is only available on 32-bit archs.
** Changed in: pixfrogger (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585058
Title:
Sync pixfrogger 1.0-4 (universe) from Debian unstable (main)
To
Sorry, I missed that - will take a look again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585058
Title:
Sync pixfrogger 1.0-4 (universe) from Debian unstable (main)
To manage notifications
Just to prove pixfrogger builds successfully in yakkety, I've uploaded
it to my PPA (https://launchpad.net/~vincent-c/+archive/ubuntu/vincents-
sandbox), where it's just finished building in the last few minutes.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
If you're test building pixfrogger with a pbuilder chroot, you'll need
to build it within a i386 chroot (i.e. pbuilder create --architecture
i386).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The following packages have unmet dependencies:
pbuilder-satisfydepends-dummy : Depends: fenix which is a virtual package and
is not provided by any available package
Depends: fenix-plugins-system which is
a virtual package and is not provided by any available
16 matches
Mail list logo
