Re: ModemManager update
With a companion libraries. ;)
↗ libmbim-1.6.0
↗ libqmi-1.8.0
↗ ModemManager-1.2.0
poma
Oh Danny boy, the pipes, the pipes are calling
>From glen to glen, and down the mountain side
The summer's gone, and all the flowers are dying
'Tis you, 'tis you must go and I must bide.
diff --git a/libqmi.spec b/libqmi.spec
index 7357544..d8b4b51 100644
--- a/libqmi.spec
+++ b/libqmi.spec
@@ -1,20 +1,20 @@
%global glib2_version 2.32.0
-%global snapshot %{nil}
-%global realversion 1.6.0
+%global realversion 1.8.0
Name: libqmi
Summary: Support library to use the Qualcomm MSM Interface (QMI) protocol
Version: %{?realversion}
-Release: 1%{snapshot}%{?dist}
+Release: 1%{?dist}
Group: Development/Libraries
License: LGPLv2+
-URL: http://www.freedesktop.org/software/libqmi
+URL: http://freedesktop.org/software/libqmi
-# If snapshot is defined, source will be a snapshot of git from the
-# master branch on the given date
-Source: %{name}-%{realversion}%{snapshot}.tar.xz
+#
+# Source from http://freedesktop.org/software/libqmi/
+#
+Source: %{name}-%{realversion}.tar.xz
BuildRequires: glib2-devel >= %{glib2_version}
BuildRequires: pkgconfig
@@ -53,9 +53,7 @@ from the command line.
%setup -q -n %{name}-%{realversion}
%build
-%configure \
- --disable-static \
- --with-tests=yes
+%configure --disable-static
make %{?_smp_mflags}
%install
@@ -86,9 +84,13 @@ make install DESTDIR=$RPM_BUILD_ROOT
%{_bindir}/qmicli
%{_bindir}/qmi-network
%{_mandir}/man1/*
+%{_libexecdir}/qmi-proxy
%changelog
+* Sat Feb 1 2014 poma - 1.8.0-1
+- Update to 1.8.0 release
+
* Fri Sep 6 2013 Dan Williams - 1.6.0-1
- Update to 1.6.0 release
diff --git a/sources b/sources
index 800d5af..964460f 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-17d6c2b404ee1eb4d1e60050fef64491 libqmi-1.6.0.tar.xz
+1c4c64c0894f691632727363abec32b8 libqmi-1.8.0.tar.xz
diff --git a/ModemManager.spec b/ModemManager.spec
index 13fa901..bf65919 100644
--- a/ModemManager.spec
+++ b/ModemManager.spec
@@ -1,4 +1,4 @@
-%global snapshot .git20130913
+
%global glib2_version 2.32
%global systemd_dir %{_prefix}/lib/systemd/system
@@ -6,19 +6,16 @@
Summary: Mobile broadband modem management service
Name: ModemManager
-Version: 1.1.0
-Release: 2%{snapshot}%{?dist}
+Version: 1.2.0
+Release: 1%{?dist}
#
-# Source from git://anongit.freedesktop.org/ModemManager/ModemManager
-# tarball built with:
-#./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var
-#make distcheck
+# Source from http://freedesktop.org/software/ModemManager/
#
-Source: %{name}-%{version}%{snapshot}.tar.xz
+Source: %{name}-%{version}.tar.xz
License: GPLv2+
Group: System Environment/Base
-URL: http://www.gnome.org/projects/NetworkManager/
+URL: https://wiki.gnome.org/Projects/NetworkManager
BuildRoot: %(mktemp -ud %{_tmppath}/%{name}-%{version}-%{release}-XX)
Requires: glib2 >= %{glib2_version}
BuildRequires: glib2-devel >= %{glib2_version}
@@ -87,11 +84,13 @@ Vala bindings for ModemManager
autoreconf -i --force
intltoolize --force
%configure \
- --enable-more-warnings=error \
+ --prefix=/usr \
+ --sysconfdir=/etc \
+ --localstatedir=/var \
+ --enable-more-warnings \
--with-udev-base-dir=%{_prefix}/lib/udev \
- --enable-gtk-doc=yes \
- --with-qmi=yes \
- --with-mbim=yes \
+ --enable-gtk-doc \
+ --with-newest-qmi-commands \
--disable-static \
--with-polkit=no \
--with-dist-version=%{version}-%{release}
@@ -141,6 +140,7 @@ gtk-update-icon-cache %{_datadir}/icons/hicolor &>/dev/null || :
%{systemd_dir}/ModemManager.service
%{_datadir}/icons/hicolor/22x22/apps/*.png
%{_mandir}/man8/*
+%{_datadir}/locale/*/LC_MESSAGES/ModemManager.mo
%files devel
%{_includedir}/ModemManager/*.h
@@ -165,6 +165,9 @@ gtk-update-icon-cache %{_datadir}/icons/hicolor &>/dev/null || :
%{_datadir}/vala/vapi/libmm-glib.*
%changelog
+* Sat Feb 1 2014 poma - 1.2.0-1
+- Update to 1.2.0 release
+
* Fri Sep 13 2013 Dan Williams - 1.1.0-2.git20130913
- Build with MBIM support
- Enable Vala bindings
diff --git a/buildsys-hates-openpty.patch b/buildsys-hates-openpty.patch
index aa61d24..4daa31e 100644
--- a/buildsys-hates-openpty.patch
+++ b/buildsys-hates-openpty.patch
@@ -1,12 +1,11 @@
diff -up ModemManager-0.4.998/src/tests/Makefile.am.foo ModemManager-0.4.998/src/tests/Makefile.am
--- ModemManager-0.4.998/src/tests/Makefile.am.foo 2011-07-06 17:59:53.711343366 -0500
+++ ModemManager-0.4.998/src/tests/Makefile.am 2011-07-06 18:00:08.971152593 -0500
-@@ -45,7 +45,6 @@ if WITH_TESTS
+@@ -3,7 +3,6 @@
noinst_PROGRAMS = \
test-modem-helpers \
test-charsets \
- test-qcdm-serial-port \
test-at-serial-port \
- test-sms-part
-
-
+ test-sms-part-3gpp \
+ test-sms-part-cdma
diff --git a/sources b/sources
index 430d5bc..4f52be2 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-055f12a1dbfc41cc4ca053c3d6ec2eee ModemManager-1.1.0.git20130913.tar.xz
+55c6cb712d9edd882f604a2ad0952515 ModemManager-1.2.0.tar.xz
diff --git a/libmbim.spec b/libmbim
ModemManager update
Danny Boy, to catch a wave. ;)
poma
diff --git a/ModemManager.spec b/ModemManager.spec
index 13fa901..f14a5c7 100644
--- a/ModemManager.spec
+++ b/ModemManager.spec
@@ -6,15 +6,12 @@
Summary: Mobile broadband modem management service
Name: ModemManager
-Version: 1.1.0
-Release: 2%{snapshot}%{?dist}
+Version: 1.2.0
+Release: 1%{?dist}
#
-# Source from git://anongit.freedesktop.org/ModemManager/ModemManager
-# tarball built with:
-#./autogen.sh --prefix=/usr --sysconfdir=/etc --localstatedir=/var
-#make distcheck
+# Source from http://freedesktop.org/software/ModemManager/
#
-Source: %{name}-%{version}%{snapshot}.tar.xz
+Source: %{name}-%{version}.tar.xz
License: GPLv2+
Group: System Environment/Base
@@ -87,11 +84,13 @@ Vala bindings for ModemManager
autoreconf -i --force
intltoolize --force
%configure \
- --enable-more-warnings=error \
+ --prefix=/usr \
+ --sysconfdir=/etc \
+ --localstatedir=/var \
+ --enable-more-warnings \
--with-udev-base-dir=%{_prefix}/lib/udev \
- --enable-gtk-doc=yes \
- --with-qmi=yes \
- --with-mbim=yes \
+ --enable-gtk-doc \
+ --with-newest-qmi-commands \
--disable-static \
--with-polkit=no \
--with-dist-version=%{version}-%{release}
@@ -141,6 +140,7 @@ gtk-update-icon-cache %{_datadir}/icons/hicolor &>/dev/null || :
%{systemd_dir}/ModemManager.service
%{_datadir}/icons/hicolor/22x22/apps/*.png
%{_mandir}/man8/*
+%{_datadir}/locale/*/LC_MESSAGES/ModemManager.mo
%files devel
%{_includedir}/ModemManager/*.h
@@ -165,6 +165,9 @@ gtk-update-icon-cache %{_datadir}/icons/hicolor &>/dev/null || :
%{_datadir}/vala/vapi/libmm-glib.*
%changelog
+* Fri Jan 31 2014 poma - 1.2.0-1
+- Update to 1.2.0 release
+
* Fri Sep 13 2013 Dan Williams - 1.1.0-2.git20130913
- Build with MBIM support
- Enable Vala bindings
diff --git a/buildsys-hates-openpty.patch b/buildsys-hates-openpty.patch
index aa61d24..4daa31e 100644
--- a/buildsys-hates-openpty.patch
+++ b/buildsys-hates-openpty.patch
@@ -1,12 +1,11 @@
diff -up ModemManager-0.4.998/src/tests/Makefile.am.foo ModemManager-0.4.998/src/tests/Makefile.am
--- ModemManager-0.4.998/src/tests/Makefile.am.foo 2011-07-06 17:59:53.711343366 -0500
+++ ModemManager-0.4.998/src/tests/Makefile.am 2011-07-06 18:00:08.971152593 -0500
-@@ -45,7 +45,6 @@ if WITH_TESTS
+@@ -3,7 +3,6 @@
noinst_PROGRAMS = \
test-modem-helpers \
test-charsets \
- test-qcdm-serial-port \
test-at-serial-port \
- test-sms-part
-
-
+ test-sms-part-3gpp \
+ test-sms-part-cdma
diff --git a/sources b/sources
index 430d5bc..1637324 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-055f12a1dbfc41cc4ca053c3d6ec2eee ModemManager-1.1.0.git20130913.tar.xz
+6e70ab7c5f96aa6a4d5612c1d5ae5bb3 ModemManager-1.2.0.tar.xz
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ModemManager update
On Sat, 01 Feb 2014 15:03:36 +0100 poma wrote: > > With a companion libraries. ;) > > ↗ libmbim-1.6.0 > ↗ libqmi-1.8.0 > ↗ ModemManager-1.2.0 Were these sent to the list for feedback on the changes? They seem fine to me from a quick glance. I don't know if there's more things that need to be rebuilt for those updates off hand. If you don't hear from Dan on it, you might consider filing a RFE bug with the patches. kevin signature.asc Description: PGP signature -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
f20, anaconda, net install and video out of range ....
Hi, I tried to help a friend upgrade his redhat 7.3 server (!) to something more modern. Since his server's BIOS had issues with booting from DVD, I setup a PXE environment on my laptop and booted the net-install (and later the live image) kernel and ram disk. After PXE boot, and leaving the live CD in the drive, Anaconda was able to boot the live environment. But when it tried to enter graphics (X) the monitor reported "out of range" errors. Changing the old LCD monitor to a 21" modern one gave the exact same results - clearly the machine is trying something very unreasonable rejected even on LCD's less than a year old. The linux text console worked fine and showed the boot process. I could even login as root and issue commands, but since this environment was a live cd, I could not figure out how to modify the X config and restart X to make this work. Adding "text" to the kernel parameters did not enable a text-based installer, and teh same out of range error apepared on the montior. Has this functionality been depricated? It seems these problems have been happening on and off on fedora's, and it is not a f20 or f18+ anacondo issue alone? Attempted workarounds included passing "text", "nomodeset", and various video= lines. None of which prevented "out of range" errors. It seems the last alternative to try is a vnc based install :( If anyone has another trick up their sleeve, I'd be interested. And if so, that trick should be added to the installer documentation (which was actually reasoanbly good, but unfortunately did not help us) Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: f20, anaconda, net install and video out of range ....
On 1 February, 2014 10:18:25 AM PST, Paul Wouters wrote: > >Hi, > >I tried to help a friend upgrade his redhat 7.3 server (!) to >something more modern. Since his server's BIOS had issues with >booting from DVD, I setup a PXE environment on my laptop and >booted the net-install (and later the live image) kernel and >ram disk. > >After PXE boot, and leaving the live CD in the drive, Anaconda >was able to boot the live environment. But when it tried to >enter graphics (X) the monitor reported "out of range" errors. > >Changing the old LCD monitor to a 21" modern one gave the exact >same results - clearly the machine is trying something very >unreasonable rejected even on LCD's less than a year old. > >The linux text console worked fine and showed the boot process. > >I could even login as root and issue commands, but since this >environment was a live cd, I could not figure out how to modify >the X config and restart X to make this work. > >Adding "text" to the kernel parameters did not enable a text-based >installer, and teh same out of range error apepared on the montior. >Has this functionality been depricated? > >It seems these problems have been happening on and off on fedora's, >and it is not a f20 or f18+ anacondo issue alone? > >Attempted workarounds included passing "text", "nomodeset", and >various video= lines. None of which prevented "out of range" errors. > > >It seems the last alternative to try is a vnc based install :( > >If anyone has another trick up their sleeve, I'd be interested. And if >so, that trick should be added to the installer documentation (which >was actually reasoanbly good, but unfortunately did not help us) > >Paul >-- >devel mailing list >devel@lists.fedoraproject.org >https://admin.fedoraproject.org/mailman/listinfo/devel >Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct You can't do a text install from a live image, but you can from DVD or net inst. We'd need the x logs to know what was going on with x startup. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin DOT net http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Packages installing files to /etc/rpm
On 31 January 2014 20:23, Ville Skyttä wrote: > kwizart color-filesystem rhughes Fixed, thanks. Richard -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: f20, anaconda, net install and video out of range ....
On Sat, 1 Feb 2014, Adam Williamson wrote: You can't do a text install from a live image, but you can from DVD or net inst. We'd need the x logs to know what was going on with x startup. I did not keep a copy of the X log, but it showed no problems. It logged various screens in resolutions any monitor should handle (like 800x600@75). It also properly probed the monitor with no errors. As far as the system was concerned, X was running without any problems. I'll try the netinst in PXE in text mode. Thanks. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: f20, anaconda, net install and video out of range ....
On Sat, 1 Feb 2014, Adam Williamson wrote: You can't do a text install from a live image, but you can from DVD or net inst. We'd need the x logs to know what was going on with x startup. Using the netinstall's isolinux/ vmlinuz,initrd and pxelinux.cfg file, the machine (physical but also VMs on my laptop) start with: [ OK ] Started Show Plymouth Boot Screen. [ OK ] Reached target Paths. [ OK ] Reached target Basic System. It then waits a _long_ time and I see: [ ] dracut-initqueue[pid]: Warning: Could not boot. [ OK ] Strated Show Plymouth Boot Screen. [ OK ] Reached target Paths. [ OK ] Reacdhed target Basic System. [ ] dracut-initqueue[pid]: Warning: Could not boot. [ ] dracut-initqueue[pid]: Warning: /dev/root does not exit and then falls into a dracut shell Looking at the report it boots a lot of things, then throws: systemd: Failed to add job sys-kernel-config.mount/start, ignoring: Invalid argument. systemd: Reloading. systemd: Failed to add job sys-kernel-config.mount/start, ignoring: Invalid argument. multimathd[71]: vda: add path (uevent) multimathd[71]: vda: spurious uevent, path already in pathvec multimathd[71]: vda: failed to get path uid multimathd[71]: uevent trigger error dracut-initqueue[474]: Warning: Could not boot. dracut-initqueue[474]: Warning: /dev/rot does not exist. Paul -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora.NEXT Products and the fate of Spins
Ralf Corsepius wrote: > Until now, I am still unable to grasp the sense of "Fedora.NEXT". > All in all, to me all I've read so far sounds like being a lot of effort > with undefined, unclear or questionable outcome. Indeed. I don't understand why we are doing that "Fedora.NEXT" thing in the first place. It's a lot of change for the sake of change, without any idea whether the output will be better than the status quo, or even whether there will be any (usable) output at all! Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora.NEXT Products and the fate of Spins
Stephen Gallagher wrote: > Right now, the vision essentially looks like: > > Fedora Products: This *is* Fedora. It comes in three flavors. I don't like the hardcoded "three" there at all, because if KDE is to ever become a full-fledged Product (which IMHO it should have been from the beginning!), it will need to change (unless you're dropping one of your 3 sacred spins). Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Fedora.NEXT Products and the fate of Spins
Stephen Gallagher wrote: > 1) Are Spins useful as they currently exist? Yes. Just see how many people do, indeed, use them. > 2) Should Spins be eliminated entirely in favor of Fedora Remixes[1]. No! HELL NO! Reducing Fedora to those 3 uninteresting "Products" would be a huge step backwards. > 3) Should Spins be considered Products-in-development? In other words, > should we only approve Spins that are targeted or destined for > "promotion" to a fully-supported Fedora Product? Maybe. It all depends on what the expectations are for something to become a Product. IMHO, it should have no more expectations than we currently have for Spins (i.e. ALL Spins should automatically become Products), in which case the question becomes moot entirely. But seeing the kind of bureaucratic processes some people are expecting Products to go through, as long as those expectations remain, I think the answer to your question 3 can only be: No! > 3b) If we treat Spins as Products-in-development, what do we do with > those Spins that don't fit that criteria? See above, there shouldn't be any. Otherwise, the answer to the previous question must be "no". In both cases, this question becomes moot. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Another questionable dependency chain -- libreoffice-writer installs log4j-chainsaw
Mikolaj Izdebski wrote: > 2) RPM doesn't differentiate between dependency scopes. Some > dependencies may be required only in some contexts, for example only for > testing, or only when using that package to compile other packages. In > the latter case one would normally put these dependencies in -devel > packages, but these are forbidden by packaging guidelines for Java. WTF??? Those guidelines must be fixed NOW! -devel stuff MUST be in -devel packages and not pollute normal packages. ALL those Java libraries should have a -devel subpackage, or if it is really not needed, a Provides: foo-devel. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Another questionable dependency chain -- libreoffice-writer installs log4j-chainsaw
Mikolaj Izdebski wrote: > That would certainly help from theoretical point of view, but that's not > really maintainable. Adding hundreds of empty packages just to improve > dependencies isn't the right way to go, IMHO. This should be fixed in > the infrastructure. IMHO, adding hundreds of empty -devel subpackages IS the way to go, if the only difference between -devel and main really is the dependencies. Stuff needed only for development belongs into -devel packages, period. Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Another questionable dependency chain -- libreoffice-writer installs log4j-chainsaw
Mikolaj Izdebski wrote: > 2) RPM doesn't differentiate between dependency scopes. Some > dependencies may be required only in some contexts, for example only for > testing, or only when using that package to compile other packages. In > the latter case one would normally put these dependencies in -devel > packages, but these are forbidden by packaging guidelines for Java. Not exactly forbidden, but there is an interesting tidbit at https://fedoraproject.org/wiki/Packaging:Java#-devel_packages "-devel packages don't really make sense for Java packages. Header files do not exist for Java packages." -devel packages can exist for many reasons besides simply providing headers, imho. -- Rex -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: ModemManager update
On 01.02.2014 18:55, Kevin Fenzi wrote: > On Sat, 01 Feb 2014 15:03:36 +0100 > poma wrote: > >> >> With a companion libraries. ;) >> >> ↗ libmbim-1.6.0 >> ↗ libqmi-1.8.0 >> ↗ ModemManager-1.2.0 > > Were these sent to the list for feedback on the changes? Everything is change. :) > They seem fine to me from a quick glance. I don't know if there's more > things that need to be rebuilt for those updates off hand. It's OK. > If you don't hear from Dan on it, you might consider filing a RFE bug > with the patches. Thanks for the advice. ;) poma https://bugzilla.redhat.com/show_bug.cgi?id=1060493 -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
